Closed Valtarr closed 7 years ago
I'll try and see whether I can reproduce
@Valtarr Did changing to the new version of Lock (as discussed over here: https://github.com/auth0/Auth0.WinformsWPF/issues/26) also fix this issue for you?
@jerriep No. Bug is still reproducible.
@Valtarr Would you mind trying out our new OIDC Client instead: https://auth0.github.io/auth0-oidc-client-net/
WPF or Windows Forms sample can be found over here: https://github.com/auth0-community/auth0-WinFormsWPF-oidc-samples/tree/master/00-Starter-Seed
@jerriep Unfortunately, OIDC client is not working with our Azure AD. Error: "Error redeeming code: Unauthorized / no description"
Will look into this for you
@Valtarr Apologies for not getting back to you
Can you please ensure that under the Settings for your Client in the Auth0 Dashboard, you have set the Client Type to Native. Then try the Auth0 OIDC Client again
@jerriep As we discovered - OIDC is not supporting JsonWebSignatureAlgoritjm HS256 - and we can not switch now to another. That's the problem.
@Valtarr Is there a reason why you cannot create a new Client which uses RS256 and then use that new one?
@Valtarr Is this still an issue for you?
As mentioned before, this library is deprecated, and should not be used anymore
@Valtarr I am closing this issue. Feel free to re-open if this is an issue
Web-page with error is shown in case of authorization of user from ADFS connection.
Steps to reproduce
Actual
Web error inside the desktop window:
Expected
Handle such situation
Don't show web error inside desktop app