Add provider param to generateResetPasswordToken#483
Open
sagar-okta wants to merge 1 commit intomasterfrom
Open
Add provider param to generateResetPasswordToken#483sagar-okta wants to merge 1 commit intomasterfrom
sagar-okta wants to merge 1 commit intomasterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Checklist
PR Type
What is the current behavior?
The
generateResetPasswordTokenmethod does not expose theproviderquery parameter in the SDK. As a result, callers cannot use the API's federation conversion feature — converting an Okta-credentialed user to a federated user — via the SDK.Issue Number: OKTA-1141679
What is the new behavior?
The
providerquery parameter (AuthenticationProviderType) is now exposed as an optional argument ongenerateResetPasswordToken. Passingprovider=FEDERATIONconverts the user's credential provider to federated, after which they must authenticate through a trusted identity provider and can no longer sign in directly with a password.This was verified live against the Okta API — calling with
provider=FEDERATIONreturns HTTP 200 and the user'scredentials.provider.typechanges toFEDERATION.Does this PR introduce a breaking change?
The new parameter is optional and fully backward compatible. Existing callers omitting
providersee no change in behavior.Other information
okta-sdk-dotnet— a separate issue should be filed there.Reviewers