0
Fixed

[BUIG]Sign in process failed due to an invalid token format.

Adam van Vliet (Chief Information Security Officer) 4 weeks ago in Dashboard updated by Beau Harrison (Software Developer) 4 weeks ago 1

Receiving this error on sign-in using a service account:

[BUIG]Sign in process failed due to an invalid token format.

Suspect missing first name / last name might have something to do with it.

Will post HAR and jwt in a private comment.

Fixed

Issue caused by Firefox's tracker blocking features, which seems to clear local storage for a site after a number of redirects when enabled. The full B2C sign in process exceeds this but if already signed in to B2C, does not. This does not happen for session storage, so I've switched Monitor use that instead.

Workaround for this issue is to sign in, get the error then reattempt sign in. The second time though the B2C flow should succeed. Alternatively, disable blocking for Monitor.