api-connectors | Libraries for connecting to the Bybit API | REST library

• It is because when you are logging into another website, it is an untrusted domain and even though the claims in the backend C# json file are hidden after authenticating through SSO, the claims output in the token received are encrypted while the email claim attribute is omitted while other claim attributes are still present in the token received even though being hidden/encrypted.

• So, the email claim attribute might be returned null in the json file as its value in the column might be missing or unknown. So, when an element is null, either the key-value pair regarding the email attribute is omitted and returns a value that corresponds to the Azure AD B2C claim data type. Thus, since the email claim attribute is a string type, it returns empty string as “” just as the email attribute is unseen in the authentication token received.

• Also, add the below claim to the custom policy output claims so that you will be able to get email as an attribute in response token as may be your custom policy might allow you to signup/sign in through multiple attribute claim types and you might not be getting email claim when using other claim types other than email.