Azure B2C Userinfo Endpoint return a Boolean

Question

Azure B2C Userinfo Endpoint return a Boolean

DisplayName-3010 101

Hello,

I am using a userinfo endpoint. If you return a claim of type boolean in the id_token if is correctly marked as a boolean in the token.
If you are using the uerinfo endpoint and create a json there, if is returned as a string with value "False" or "True". Is there a possibility to configure this, or is this a bug or non-implemented feature in the current solution?

Example Userinfo:
{
"sub": "********",
"email": "someemail@tiedtlaw email .com",
"locale": "de",
"extension_residency": "False"
}

Example Token

{
"typ": "JWT",
"alg": "RS256",
"kid": "****"
}.{
"exp": 1651119806,
"nbf": 1651033406,
"ver": "1.0",
"iss": "****",
"sub": "*",
"aud": "****",
"acr": "****",
"nonce": "defaultNonce",
"iat": 1651033406,
"auth_time": 1651033406,
"locales": "de",
**extension_residency": false
}.[Signature]

Answer 1

AmanpreetSingh-MSFT 55,551

Hi @DisplayName-3010 • Thank you for reaching out.

Unfortunately, as of now, you cannot configure how it should be returned as a response to calling the UserInfo endpoint. So, it is not a bug but a non-implemented feature. You can post an idea regarding this at the Azure Feedback portal.

The UserInfo endpoint is designed to return the boolean attributes as either true or false, depending on the default value configured for the attribute in the custom policy.

For example, if the value of the boolean attribute (extension_boolval in this case) in the token is false but the RP (signup/sign-in) file is configured with the DefaultValue for this attribute as true, the UserInfo endpoint will return the value as True.

Value of the boolean attribute in the Token:
Configuration in the signup/signin xml file:
Response from UserInfo endpoint:

-----------------------------------------------------------------------------------------------------------

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

DisplayName-3010 101 Reputation points

2022-05-04T07:07:47.557+00:00

So a boolean in a token is returned as
{
"extension_boolean": false
}

But in the userinfo endpoint as
{
"extension_boolean": "False"
}

Even though both are json. Why is there a difference between the two representations in the json? One has quotes, and one does not have quotes.

The claims schema is the same, so why is the behavior not the same for the output?
AmanpreetSingh-MSFT 55,551 Reputation points

2022-05-05T02:33:09.753+00:00

@DisplayName-3010 • As I have mentioned in my response above, the output of the UserInfo endpoint depends on the DefaultValue of the output claim specified in the RP file. So, It returns the default value as a string (in quotes) and not as a boolean value because it is not dynamically changed when fetched from the UserInfo endpoint. On the other hand, in the token, the value is returned as a boolean value that can be dynamic and the token can have the value as either True or False.

Even though, both the token and the UserInfo output is in JSON format, the type of the value depends on how it is being passed. In the UserInfo endpoint, it is passed as a string that's why there are quotes and in the token, it is passed as a boolean value, which is why there are no quotes.

Hope this clarifies. Please do Share your feedback about the answer and "Accept the answer" if the information helped you.
AmanpreetSingh-MSFT 55,551 Reputation points

2022-05-06T10:58:09.783+00:00

@DisplayName-3010 • Just checking if you have any further questions.
DisplayName-3010 101 Reputation points

2022-05-10T12:19:37.27+00:00

@AmanpreetSingh-MSFT : I did not get notified of your answer. So is it possible to return a boolean and not a string on the userinfo endpoint or will the userinfo endpoint always return a string for any kind of claim?

If you talk about how a value is being passed you only talk about The creation of the token/creation of the userinfo response?

Because in the implementation we have in both cases the information is read from the Active Directorya and stored in a claim defined with a ClaimsType of Type Boolean.
AmanpreetSingh-MSFT 55,551 Reputation points

2022-05-10T12:36:15.597+00:00

@DisplayName-3010 • When the information is passed to the UserInfo endpoint, there is no Boolean logic applied. Just the default value is checked and returned as a string in the UserInfo response JSON. This behavior cannot be customized/modified as of now.

When the same claim is passed in the token, the boolean logic is applied to determine whether the value should be returned as true or false based on a given scenario/logic/configuration.
DisplayName-3010 101 Reputation points

2022-05-11T09:57:44.227+00:00

Ok this is understandable for me. Even though we do not use the default value.
A technical profile with OutPutToken JSON always returns and information it has as a json string. A token issuer generates a token with string, numbers and booleans.
This is a non implemented feature, which I opened a idea to change as you suggested.
Tobias Schmidt 76 Reputation points

2022-05-12T06:12:30.917+00:00

Thank you for all those answers.

Is there any plan to support different types in the UserInfo response?
Currently, it's not possible to comply with the OpenID Connect standard as it specifies booleans (e.g. email_verified) & nested JSONs (e.g. address) in the response.
AmanpreetSingh-MSFT 55,551 Reputation points

2022-05-19T06:22:39.053+00:00

@32613837 · Thank you for reaching out. AFAIK, this is not yet planned. There must be active feedback by @DisplayName-3010 regarding this feature that you can upvote.

@DisplayName-3010 Could you please share the link to the idea that you have posted on the feedback portal so that others looking for this feature can upvote that. I will also bring that idea to the attention of the product group.

Azure B2C Userinfo Endpoint return a Boolean

0 additional answers

Activity