You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Preconditions:
We're using our OIE instance at dev-auth.partssource.com
We use the self-hosted sign-in widget and the forgot password worfklow works as expected
We've verified the authenticator setup and the okta-idx-dotnet SDK configuration (endpoint, client id, etc)
It is expected that the login id that initiates the recover password workflow will receive an email with a "magic" link to reset their password. This works as expected in our test environment with the self-hosted sign-in widget. This does not happen when the recover password workflow is initiated for the same user from the okta-idx-dotnet SDK.
Make a call to the SelectRecoveryAuthenticatorAsync method with the authenticator id from the "email" authenticator
Observe the null reference exception. We debugged through the source code and found that the property "currentEnrollment.recover" is null in "SelectRecoveryAuthenticatorAsync"
Additional Information?
No response
.NET Version
dotnet --version
6.0.302
SDK Version
okta-idx-dontnet v2.2.1
OS version
Microsoft Windows 11 Pro
Version
10.0.22000
BuildNumber
22000
OSArchitecture
64-bit
The text was updated successfully, but these errors were encountered:
@mgpartssource Thanks for bringing this to our attention! I've entered an internal ticket to address the issue; it will need to be prioritized against other work.
@mgpartssource I apologize for the inconvenience and thank you for your patience while we review this issue! After initial investigation I'd like to ensure we address the issue specifically as it relates to your scenario and configuration. Please reach out to our support team at developers@okta.com - this will enable us to work with you directly and discuss details about your configuration in a less public manner; the support team will coordinate with us, the development team, to reproduce the issue and implement an appropriate fix.
Describe the bug?
Preconditions:
We're using our OIE instance at dev-auth.partssource.com
We use the self-hosted sign-in widget and the forgot password worfklow works as expected
We've verified the authenticator setup and the okta-idx-dotnet SDK configuration (endpoint, client id, etc)
Issue:
When initiating the forgot password workflow from the okta-id-dotnet SDK we receive a null reference exception on the call to to SelectRecoveryAuthenticatorAsync as outlined on the guide in step 5 here: https://developer.okta.com/docs/guides/oie-embedded-sdk-use-case-pwd-recovery-mfa/aspnet/main/#_5-make-a-call-to-the-selectrecoveryauthenticatorasync-method
What is expected to happen?
It is expected that the login id that initiates the recover password workflow will receive an email with a "magic" link to reset their password. This works as expected in our test environment with the self-hosted sign-in widget. This does not happen when the recover password workflow is initiated for the same user from the okta-idx-dotnet SDK.
What is the actual behavior?
When initiating the forgot password workflow from the okta-id-dotnet SDK we receive a null reference exception on the call to to SelectRecoveryAuthenticatorAsync as outlined on the guide in step 5 here: https://developer.okta.com/docs/guides/oie-embedded-sdk-use-case-pwd-recovery-mfa/aspnet/main/#_5-make-a-call-to-the-selectrecoveryauthenticatorasync-method
Reproduction Steps?
Follow steps 3 and 5 here https://developer.okta.com/docs/guides/oie-embedded-sdk-use-case-pwd-recovery-mfa/aspnet/main/#_3-make-a-call-to-the-recoverpasswordasync-method
Observe the null reference exception. We debugged through the source code and found that the property "currentEnrollment.recover" is null in "SelectRecoveryAuthenticatorAsync"
Additional Information?
No response
.NET Version
dotnet --version
6.0.302
SDK Version
okta-idx-dontnet v2.2.1
OS version
Microsoft Windows 11 Pro
Version
10.0.22000
BuildNumber
22000
OSArchitecture
64-bit
The text was updated successfully, but these errors were encountered: