Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Azure AD B2C seems to be creating "unknown" users when refreshing id_token?

It seems like a removed user account in Azure AD B2C is being resurrected (or recreated) when an application is requesting a new token (refresh token). In our case a mobile app requesting tokens.

When user accounts have been deleted, users with the same email address are suddenly visible with the name "unknown" but the same email addresss.

The Audit Log seems to start with a id_token request for users that have activity the last 7 days.

Isn't this strange if my assumption is correct? A removed user should never be able to refresh a token since the whole point of refresh tokens is that you can't refresh it if you no longer have access.

List of "unknown" users:

Unknown users

Audit Log for example user:

enter image description here

like image 598
Jonas Stensved Avatar asked Mar 16 '18 10:03

Jonas Stensved


People also ask

What is refresh token in Azure AD?

The refresh token is used to obtain new access/refresh token pairs when the current access token expires. Refresh tokens are also used to acquire extra access tokens for other resources. Refresh tokens are bound to a combination of user and client, but aren't tied to a resource or tenant.

How long refresh token is valid for Azure AD?

The default lifetime of the token is 1 hour.

What is UserStrongAuthClientAuthNRequiredInterrupt?

UserStrongAuthClientAuthNRequiredInterrupt - Strong authentication is required and the user did not pass the MFA challenge.


1 Answers

I have nailed down this issue with help from Microsoft support. It seems to be a user issue (not an Azure AD issue which is good) due to policies not enforcing users to set a DisplayName when registering.

Note to self: Users saying they haven't registered doesn't always mean they haven't.

like image 69
Jonas Stensved Avatar answered Dec 08 '22 10:12

Jonas Stensved