<-- Back

Unable to login Studio Pro using Web Sign in option: Encrypting refresh token failed

Issue

When attempting to login Studio Pro using Go to Web Sign In button, the below error is thrown, blocking the user to login Studio Pro.

ERROR Mendix.Modeler.UserManagement.TokenStore Encrypting refresh token failed
Internal.Cryptography.CryptoThrowHelper+WindowsCryptographicException: The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation.
at System.Security.Cryptography.ProtectedData.ProtectOrUnprotect(Byte[] inputData, Byte[] optionalEntropy, DataProtectionScope scope, Boolean protect)
at System.Security.Cryptography.ProtectedData.Protect(Byte[] userData, Byte[] optionalEntropy, DataProtectionScope scope)
at Mendix.Modeler.UserManagement.CredentialProtection.Protect(Byte[] data) in Mendix.Modeler.Core\UserManagement\CredentialProtection.cs:line 41
at Mendix.Modeler.UserManagement.CredentialProtection.Encrypt(String original) in Mendix.Modeler.Core\UserManagement\CredentialProtection.cs:line 16
at Mendix.Modeler.UserManagement.CredentialProtection.Encrypt(SecureString original) in Mendix.Modeler.Core\UserManagement\CredentialProtection.cs:line 21
at Mendix.Modeler.UserManagement.TokenStore.StoreCredentials(SecureString accessToken, SecureString refreshToken, SecureString idToken, Int32 expiresIn) in Mendix.Modeler.Core\UserManagement\TokenStore.cs:line 43
ERROR Mendix.Modeler.UserManagement.AuthorizeRedirectListener An error occurred while processing the SSO callback request.

Environment

Studio Pro 9.1.0 and newer

Cause

This error occurs due to local system configuration in Microsoft Windows 10 and 11, specifically a security update from Windows. This error suggests there is an issue with the encryption of the refresh token in the Windows machine, likely related to user authentication and permissions.

Solution/Workaround

As the issue lies within the Windows machine the user is using and not related to Studio Pro, the next steps should be taken:

Internal information related

  •  232301, 233806, 123418

Additional information

Other documentation: Discussion related to the error in StackExchange 

Have more questions? Submit a request

0 Comments

Article is closed for comments.

To provide feedback, please open a ticket here. Don't forget to include the article's URL along with the feedback you would like to provide.