-
Notifications
You must be signed in to change notification settings - Fork 262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support email callback and password reset in widget #1014
Conversation
63edc19
to
7894237
Compare
Codecov Report
@@ Coverage Diff @@
## dev-6 #1014 +/- ##
==========================================
- Coverage 92.52% 92.42% -0.10%
==========================================
Files 134 134
Lines 3664 3722 +58
Branches 751 775 +24
==========================================
+ Hits 3390 3440 +50
- Misses 274 282 +8
Continue to review full report at Codecov.
|
8496b7a
to
97e68ef
Compare
@@ -59,9 +66,77 @@ This module provides convenience methods to support popular scenarios to communi | |||
|
|||
### Concepts | |||
|
|||
#### Flow | |||
|
|||
In addition to the default authentication flow, this SDK supports several pre-defined flows, such as [register](#idxregister) and [recoverPassword](#idxrecoverpassword). A flow can be started by calling one of the available [flow entrypoints](#flow-entrypoints) or by passing a valid flow identifier string to [`startTransaction`](#idxstarttransaction). The `flow` is saved with the transaction which enables the [proceed](#idxproceed) method to corrrectly handle remediations without additional context. Starting a new flow discards any existing in-progress transaction of a different type. For example, if an authentication flow is in-progress, a call to [authenticate](#idxauthenticate) or [proceed](#idxproceed) will continue using the current transaction but a call to [register](#idxregister) or [recoverPassword](#idxrecoverpassword) will start a new transaction. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe mention their Org configurations matter for flows like recoverPassword
and register
? I think authenticate is the only flow that works "out-of-the-box"
bf47a7a
to
5e76c5d
Compare
docs/idx.md
Outdated
|
||
The `flow` will be set to `default` unless otherwise specified in [`idx.startTransaction`](#idxstarttransaction) | ||
|
||
#### Callbacks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: maybe Redirect Callbacks
?
505a6bd
to
76edf7a
Compare
email verify callback contains otp parameter adds new option withCredentials adds new option codeChallenge pass authenticator if password is provided up front use jasmine framework in wdio improve layout in test app add more time for token renew tests prefer login direct, avoid issue with popup OKTA-454796 add exchangeCodeForTokens option loosen remediate restrictions on default flow update samples throw exceptions from run (breaking change) consolidate idx interface under the idx namespace activationToken and recoveryToken as config option
76edf7a
to
7f54738
Compare
stateTokenExternalId
state
andotp
otp
to idx pipeline to statisfycredentials.passcode
on a challenge authenticator of type != "password" (basically an alias forverificationCode
)exchangeCodeForTokens
option for IDX methods (SIW will pass false, it has its own logic to support server-side web apps)saveLastResponse
. if false, idx responses will not be cached