Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fixed minor spelling and grammar in readme, directory name #609

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fixed minor spelling and grammar in readme, directory name #609

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
0 ...m-claims-provider/poicy/PasswordReset.xml → ...-claims-provider/policy/PasswordReset.xml
View file
Open in desktop
File renamed without changes.
0 ...tom-claims-provider/poicy/ProfileEdit.xml → ...om-claims-provider/policy/ProfileEdit.xml
View file
Open in desktop
File renamed without changes.
0 ...-claims-provider/poicy/SignUpOrSignin.xml → ...claims-provider/policy/SignUpOrSignin.xml
View file
Open in desktop
File renamed without changes.
0 ...ims-provider/poicy/TrustFrameworkBase.xml → ...ms-provider/policy/TrustFrameworkBase.xml
View file
Open in desktop
File renamed without changes.
0 ...ovider/poicy/TrustFrameworkExtensions.xml → ...vider/policy/TrustFrameworkExtensions.xml
View file
Open in desktop
File renamed without changes.
4 changes: 2 additions & 2 deletions policies/custom-claims-provider/readme.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
# Azure Active Directory B2C: Custom claims provider
This sample application is a custom OpenId connect claims provider that federates with Azure AD B2C over OIDC protocol. When a user sign-in or sign-up, the custom policy calls a REST API that checks the user profile status and the application ID. If the application requires certain properties that aren't exist in the user profile, the REST API returns an indicator to B2C to redirect the user to the custom claims provider to complete the missing attributes. The REST API response also contains an encrypted unique global ID. This unique global Id is stored in Azure Blob Storage table along with the user object Id.
This sample application is a custom OpenId connect claims provider that federates with Azure AD B2C over OIDC protocol. When a user sign-in or sign-up, the custom policy calls a REST API that checks the user profile status and the application ID. If the application requires certain properties that don't exist in the user profile, the REST API returns an indicator to B2C to redirect the user to the custom claims provider to complete the missing attributes. The REST API response also contains an encrypted unique global ID. This unique global Id is stored in Azure Blob Storage table along with the user object Id.

The solution utilizes the OpenID protocol. Azure AD B2C redirects the user to the custom claims provider (like any OIDC social providers). The request contains also a unique request ID generated by the REST API.

The custom claims provider, decrypt the request Id, checks that the request id exists in Azure Table. Also make sure the request comes from the same IP source.
The custom claims provider decrypts the request Id and checks that the request id exists in Azure Table. It also makes sure the request comes from the same IP source.

By calling the Azure Table, the custom claims provider has the user object Id. With the user object Id, the claims provider is able to update the user profile. After user complete the profile editing the custom claims provider removed the entity from Azure Blob storage.

Expand Down