From fbea2ff2ac7b21147fc6e7eed6a6570832abc0d6 Mon Sep 17 00:00:00 2001 From: Rob Carlson Date: Mon, 22 Apr 2024 21:40:11 -0400 Subject: [PATCH] Fixed minor spelling and grammar in readme, directory name --- .../{poicy => policy}/PasswordReset.xml | 0 .../custom-claims-provider/{poicy => policy}/ProfileEdit.xml | 0 .../{poicy => policy}/SignUpOrSignin.xml | 0 .../{poicy => policy}/TrustFrameworkBase.xml | 0 .../{poicy => policy}/TrustFrameworkExtensions.xml | 0 policies/custom-claims-provider/readme.md | 4 ++-- 6 files changed, 2 insertions(+), 2 deletions(-) rename policies/custom-claims-provider/{poicy => policy}/PasswordReset.xml (100%) rename policies/custom-claims-provider/{poicy => policy}/ProfileEdit.xml (100%) rename policies/custom-claims-provider/{poicy => policy}/SignUpOrSignin.xml (100%) rename policies/custom-claims-provider/{poicy => policy}/TrustFrameworkBase.xml (100%) rename policies/custom-claims-provider/{poicy => policy}/TrustFrameworkExtensions.xml (100%) diff --git a/policies/custom-claims-provider/poicy/PasswordReset.xml b/policies/custom-claims-provider/policy/PasswordReset.xml similarity index 100% rename from policies/custom-claims-provider/poicy/PasswordReset.xml rename to policies/custom-claims-provider/policy/PasswordReset.xml diff --git a/policies/custom-claims-provider/poicy/ProfileEdit.xml b/policies/custom-claims-provider/policy/ProfileEdit.xml similarity index 100% rename from policies/custom-claims-provider/poicy/ProfileEdit.xml rename to policies/custom-claims-provider/policy/ProfileEdit.xml diff --git a/policies/custom-claims-provider/poicy/SignUpOrSignin.xml b/policies/custom-claims-provider/policy/SignUpOrSignin.xml similarity index 100% rename from policies/custom-claims-provider/poicy/SignUpOrSignin.xml rename to policies/custom-claims-provider/policy/SignUpOrSignin.xml diff --git a/policies/custom-claims-provider/poicy/TrustFrameworkBase.xml b/policies/custom-claims-provider/policy/TrustFrameworkBase.xml similarity index 100% rename from policies/custom-claims-provider/poicy/TrustFrameworkBase.xml rename to policies/custom-claims-provider/policy/TrustFrameworkBase.xml diff --git a/policies/custom-claims-provider/poicy/TrustFrameworkExtensions.xml b/policies/custom-claims-provider/policy/TrustFrameworkExtensions.xml similarity index 100% rename from policies/custom-claims-provider/poicy/TrustFrameworkExtensions.xml rename to policies/custom-claims-provider/policy/TrustFrameworkExtensions.xml diff --git a/policies/custom-claims-provider/readme.md b/policies/custom-claims-provider/readme.md index 54d280e1..e81a33eb 100644 --- a/policies/custom-claims-provider/readme.md +++ b/policies/custom-claims-provider/readme.md @@ -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.