DOMException: Failed to execute 'atob' on 'Window': The string to be decoded is not correctly encoded.

[Michael-006]

Core Library

MSAL.js (@azure/msal-browser)

Core Library Version

?

Wrapper Library

MSAL Angular (@azure/msal-angular)

Wrapper Library Version

3.0.4

Public or Confidential Client?

Public

Description

When having special characters in the displayName like my tester special charactersčćęèéêëėįìíîï msal throws an error "Failed to execute 'atob' on 'Window': The string to be decoded is not correctly encoded."

After this error I'm getting:

ClientAuthError: token_parsing_error: Token cannot be parsed. Please review stack trace to determine root cause. Failed with error: InvalidCharacterError: Failed to execute 'atob' on 'Window': The string to be decoded is not correctly encoded.

Error Message

DOMException: Failed to execute 'atob' on 'Window': The string to be decoded is not correctly encoded.

Msal Logs

No response

MSAL Configuration

not relevant

Relevant Code Snippets

try {
    const oe = S(Q);
    return JSON.parse(oe)
} catch (oe) {
    throw d.e.createTokenParsingError(oe)
}

Reproduction Steps

Set display name to my tester special charactersčćęèéêëėįìíîï

Expected Behavior

no error, should decode correctly

Identity Provider

Azure B2C Custom Policy

Browsers Affected (Select all that apply)

Chrome

Regression

No response

Source

External (Customer)

[Mexx77]

we see the same issue with the special character ł in the lastname of the user

[jansepke]

possible duplicate of #6476

[microsoft-github-policy-service]

This issue requires attention from the MSAL.js team and has not seen activity in 5 days. @hectormmg please follow up.

[fredliex]

in commit 2ef47fe , some code are missing.

microsoft-authentication-library-for-js/lib/msal-browser/src/encode/Base64Decode.ts

Line 24 in b69ed83

const binString = atob(base64String);

should be as follows

const binString = atob(base64String.replace(/-/g, "+").replace(/_/g, "/"));

[tnorling]

This has been fixed in 3.2.0

[MohanMugi]

@fredliex you are a life saver...
Thank you!

[MaikL]

Are there different rollout phases for this bugfix?
In the AzureEU Cloud I still get the same error, when I try to add a password to my gateway.

Uncaught (in promise) DOMException: Failed to execute 'atob' on 'Window': The string to be decoded is not correctly encoded.

[tnorling]

Are there different rollout phases for this bugfix? In the AzureEU Cloud I still get the same error, when I try to add a password to my gateway.

Uncaught (in promise) DOMException: Failed to execute 'atob' on 'Window': The string to be decoded is not correctly encoded.

This is a client library, not a service, there is no "rollout". Your application or whatever is invoking MSAL.js will need to install and deploy the latest version with the fix.

[MaikL]

OK, sorry I missed to reference some circumstances.
The Error occurs on the Gateway configuration page of Power BI (https://app.powerbi.com/groups/me/gateways).
When I try to enter the username and password for a Basic Authentification Method. So I think this is on Microsofts side to add these changes.

[MohanMugi]

Hi, Try this solution, it should work. #6492 const binString = atob(base64String.replace(/-/g, "+").replace(/_/g, "/")); Best Regarding, Mohan Palanisamy

…

On Mon, Nov 27, 2023 at 1:35 PM Maik Lüdeke ***@***.***> wrote: Are there different rollout phases for this bugfix? In the AzureEU Cloud I still get the same error, when I try to add a password to my gateway. Uncaught (in promise) DOMException: Failed to execute 'atob' on 'Window': The string to be decoded is not correctly encoded. — Reply to this email directly, view it on GitHub <#6492 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC5SW7KK6LJEVIBUB54XH43YGRCVTAVCNFSM6AAAAAA44YVHSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRXGMZDKMZTG4> . You are receiving this because you commented.Message ID: <AzureAD/microsoft-authentication-library-for-js/issues/6492/1827325337@ github.com>

[MaikL]

I am sorry, my problem is solved. The error was, that I installed the "standard Gateway" not the "personal Gateway".
Why there is no specific error, which hints to this problem is beyond my horizon.