Releases: okta/okta-sdk-dotnet
Okta.Sdk v6.0.0-beta01
We're excited to drop the first prerelease version of the new OASv3 compatible Okta Management SDK for .NET! 🎉
⚠️ Prerelease warning
This version is beta-quality. We'd love for you to play with it and give us your thoughts, but we don't recommend using it in production applications. Based on the feedback we receive, we'll be iterating it towards a stable 6.0 release over the next few weeks. There may be minor breaking changes to the interfaces before stabilizing at 6.0.
Note: The 6.0.0-beta series is located in the oasv3 branch
What's included today
In this first beta version, we ported some of the existing features to the new SDK:
- Inline configuration, configuration via environment variables, appsettings.json, or YAML files
- Manual Pagination for collections
- Default retry strategy for 429 HTTP responses and ability to provide your own strategy
- Web Proxy is only available via the inline configuration
Upgrading
This version uses a new Open API generator and introduces several breaking changes, so we've rolled over the major version number to 6.0.0. Check out the migrating guide for more info!
If you've been using the existing Okta SDK (version 5.x), you can opt to try this new version (which will require some code changes), or stick with what you already have. The 5.x series of the SDK is still supported.
Okta.Sdk v5.6.0
- Update Open API spec to 2.12.0
- Add
Application.UpdateApplicationPolicyAsync
method - Add
APPLE
as aLogCredentialProvider
option - Add support for
AllowedOktaApps
in Scopes - Add
IframeEmbed
as aScopeType
option
Okta.Sdk v5.5.0
v5.5.0
- Add support for Email template operations.
Okta.Sdk v5.4.1
Bug Fixes
- Fix the issue "SDK doesn't retry a call to the server when the token has expired" (PrivateKey mode) (#535)
Okta.Sdk v5.4.0
- Add support for Application provisioning connection operations
- Add support for Application features operations
- Add support for Org2Org applications
Okta.Sdk v5.3.2
Okta.Sdk v5.3.1
Features
- Add
VerifyUserFactorResponse.GetTransactionId
method to simplify access to the transaction ID of theVerifyUserFactorResponse
where appropriate. The transaction ID is further used with theGetFactorTransactionStatusAsync
operation. See Issue a Push Factor challenge for details. (#507)
Okta.Sdk v5.3.0
Features
- Add ability to use pre-requested access tokens for authentication (#508)
- Regenerate code using the open API spec v2.9.2
- Add new models and operations to support Brands API's endpoints
- Add new models and operations to support OIE policies
Updates
- Group.AssignRoleAsync(IAssignRoleRequest assignRoleRequest, string disableNotifications, CancellationToken cancellationToken = default(CancellationToken)); is not marked as obsolete. Use Group.AssignRoleAsync(IAssignRoleRequest assignRoleRequest, bool? disableNotifications = null, CancellationToken cancellationToken = default(CancellationToken)); instead.
- UsersClient. AssignRoleToUserAsync(IAssignRoleRequest assignRoleRequest, string userId, string disableNotifications, CancellationToken cancellationToken = default(CancellationToken)); is not marked as obsolete. Use UsersClient. AssignRoleToUserAsync(IAssignRoleRequest assignRoleRequest, string userId, bool? disableNotifications = null, CancellationToken cancellationToken = default(CancellationToken)); instead.
Okta.Sdk v5.2.1
Updates
- Remove FlexibleConfiguration dependency and use Microsoft Configuration instead
Okta.Sdk v5.2.0
Features
-
Regenerated code open API spec v2.7.1
-
Added new models and operations to support the following APIs:
-
Added an overload for
GroupsClient.DeleteGroupRuleAsync
method. Now you can specify theremoveUsers
parameter indicating whether to keep or remove users from groups assigned by this rule.
Bug Fixes
- Fixed
GroupsClient.ListGroups
filter parameter doesn't work. Replaced withsearch
parameter. - Fixed issue on
AuthorizationServerPolicyRule.ActivateAsync
.