You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"In order for B2C to manage this metadata for us we will need to upload the certificate we generated to sign our id_token_hint to B2C. We can either upload the pfx + password or just the cer file to the B2C key container."
"In the "Policy Keys" blade, click Add to create a new key and select Upload in the options".
"Give it a name, something like Id_Token_Hint_Cert and select key type to be RSA and usage to be Signature".
Key type and signature options are not available for "Upload" only for "Generate".
You cannot upload a cer file. If you try (and ignore password), it complains that it is not Base64 encoded.
You have to use a .pfx file.
The text was updated successfully, but these errors were encountered:
For this policy:
samples/policies/invite/
"SignUp with email invitation"
"In order for B2C to manage this metadata for us we will need to upload the certificate we generated to sign our id_token_hint to B2C. We can either upload the pfx + password or just the cer file to the B2C key container."
"In the "Policy Keys" blade, click Add to create a new key and select Upload in the options".
"Give it a name, something like Id_Token_Hint_Cert and select key type to be RSA and usage to be Signature".
Key type and signature options are not available for "Upload" only for "Generate".
You cannot upload a cer file. If you try (and ignore password), it complains that it is not Base64 encoded.
You have to use a .pfx file.
The text was updated successfully, but these errors were encountered: