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
It seems the Challenger and SignInForm in Toolkit support username/password but not oAuth2. However, our clients may access both types of sources, so I need a challenger to handle both situations. Right now, my approach is this:
When the function CreateCredentialAsync(CredentialRequestInfo info) is called, try oAuth2 first.
If oAuth2 failed, try username/password with the SignInForm.
This approach is kind of working, but not a good solution. The CredentialRequestInfo parameter does not tell whether it is oAuth2 or username/password, and both of them belong to AuthentiationType.Token enum. So, it seems I can only try both.
Is there a better way to do it? In addition, is the Challenger and SignInForm in Toolkit going to support oAuth2 later?
Thanks.
The text was updated successfully, but these errors were encountered:
It seems the Challenger and SignInForm in Toolkit support username/password but not oAuth2. However, our clients may access both types of sources, so I need a challenger to handle both situations. Right now, my approach is this:
This approach is kind of working, but not a good solution. The CredentialRequestInfo parameter does not tell whether it is oAuth2 or username/password, and both of them belong to AuthentiationType.Token enum. So, it seems I can only try both.
Is there a better way to do it? In addition, is the Challenger and SignInForm in Toolkit going to support oAuth2 later?
Thanks.
The text was updated successfully, but these errors were encountered: