This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(70.4, 42%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAP%3C/text%3E%3C/svg%3E)
Hi,
I have an Azure AD B2C custom policy (SAML protocol) being used by an application 'A' setup and working fine. I want to integrate another application 'B' using OpenId protocol. This application 'B' is hosted in AWS and uses AWS Cognito user pool.
I have the OpenId Custom Policy defined in B2C and works fine when testing using https://jwt.ms. I configure this OpenId policy in AWS Cognito under Federated Identity Provider and using the configuration from B2C registered app id and custom policy claims.
When I try to test this integration using a sample web app, it looks like the authentication is happening from B2C, however not all claims from the Custom Policy are being passed on to AWS Cognito. Correct claims mapping are put in place in AWS.
Hi @Anand Patil , what are the claims being passed? Some tokens cannot be passed. Also, have you checked the logs for any errors? Please let me know and I can help you further.
Best,
James
The claims being passed are - email, firstName, lastName and four custom attributes that are defined in the custom policy. These four custom attributes are fetched using a REST-API call from the custom policy itself.