azure-ad-b2c

Azure AD B2C - Token validation does not work

不羁的心 提交于 2019-11-29 05:18:41
I would like to use Azure AD B2C but have several difficulties using it. One problem I have is to validate the signature of the token. First I wanted to validate the token "manually" using jwt.io. According to the Microsoft Docs , validating the signature should work like this: Your app can use the kid claim in the JWT header to select the public key in the JSON document that is used to sign a particular token. It can then perform signature validation by using the correct public key and the indicated algorithm. My understandig: Grab the kid value out of the header, lookup the key in the

Request Access Token in Postman for Azure AD B2C

帅比萌擦擦* 提交于 2019-11-29 02:17:57
How can I request an Access Token in Postman against an Azure AD B2C tenant? I tried taking the url from Run Now in the Azure portal and putting that in the Auth Url but that produces the following error: Update Following Chris's answer, I'm now past the above error. I'm able to sign-in but still can't get an access token: AADB2C90085: The service has encountered an internal error. Please reauthenticate and try again. Correlation ID: 45c56d47-4739-465f-8e02-49ba5b3a1b86 Timestamp: 2017-11-16 15:27:52Z Using @Chris Padgett's answer , I was able to get it working using the Implicit Grant Type

Multi-tenant Azure AD in Azure AD B2C

你。 提交于 2019-11-29 00:22:44
I was following the answer here: Multi-Tenant Azure AD Auth in Azure AD B2C with Custom Policies And the walkthrough here: https://github.com/Azure-Samples/active-directory-b2c-advanced-policies/blob/0129fc013ae5e66a3ee0046a5d0db2e8120d8f8e/Walkthroughs/IdP-AzureAD.md But I wasn't able to login, the error message is something along the line: AADB2C: An exception has occured. Correlation ID: <GUID>. Timestamp: <Time> Furthermore, when viewing the walkthrough in latest master, the whole page has been removed and now only contains the link to https://docs.microsoft.com/en-us/azure/active

Change default picture - registration flow - AZURE - ADB2C

我怕爱的太早我们不能终老 提交于 2019-11-28 14:25:59
In the ADB2C user registration flow you have an picture on the left & the form on the right. Is there an easy way to change the picture on the left? I don't want to redesign the whole page. Full customization which includes your own HTML/CSS is available for all the Azure AD B2C user flows including the "sign-up or sign-in policies" which offers a combined - registration and login - policy. The "sign-in" policy type is the only one that offers the ability to customize via the "company branding" feature which needs only a picture upload. All other flows require upload of HTML/CSS content. A

Can I disable sign-up in Azure AD B2C?

拜拜、爱过 提交于 2019-11-28 12:25:27
Can I disable sign-up in Azure AD B2C? In other words, I don't want customers to sign up accounts by themselves, I want it to be done only by admin in Azure. Thanks. Built-in Policies Yes, only define a Sign-in policy . Do not define a Sign-up or Sign-in policy nor a Sign-up policy . Custom Policies The problem with a sign-in only policy is you only have basic UI customization options. You do not get the full set of features as described here . With custom policies, you can define a Sign-Up/Sign-In policy and then disable the Sign-Up portion. This allows for the same level if UI customization

Azure Portal: Bad Request - Request Too Long

纵饮孤独 提交于 2019-11-28 09:07:01
I just received the following error when I tried to run a built-in b2c edit policy from portal.azure.com . I have 2 tabs of the portal open. Why am I receiving this error? Bad Request - Request Too Long HTTP Error 400. The size of the request headers is too long. Note: I experienced this same error message when testing active-directory-b2c-dotnet-webapp-and-webapi sample project . The reason provided was I was sending too many cookies. Is it the same problem? If it is the same problem, shouldn't stale cookies be deleted before creating new ones? I do see a lot of cookies for https://login

Local account created in AzureAD B2C with “forceChangePasswordNextLogin” cannot login anymore after initial password change

你离开我真会死。 提交于 2019-11-28 09:05:47
问题 I have a WebAPI creating local account in an AzureAD B2C tenant through the AzureAD Graph API. When users are created, they receive an invitation email with a temporary password. User is created in the Graph API with a password profile to force them to change their temporary password on first login. user.PasswordProfile = new PasswordProfile(); user.PasswordProfile.Password = GetTemporaryPassword(); user.PasswordProfile.ForceChangePasswordNextLogin = true; When the user login for the first

Azure AD B2C - Use Graph API to populate “Authentication Email”

不羁的心 提交于 2019-11-28 08:26:57
问题 Is there a way we can populate the “Email” field for the user via Graph API in Azure AD B2C. There is a section “Authentication contact info” under the user profile, which has a field “Email” which is a read-only field when accessed via Graph API and cannot be populated programmatically. I am able to use Graph API to populate the “Alternate email”. However for the reset password policy (user clicks the forgot password link), the “Email” field is a required field I am unable to use the

Azure AD B2C Token Issue

谁都会走 提交于 2019-11-28 05:41:03
问题 As an enterprise, we would like to use Azure AD B2C and we have internal and external users. Azure AD helps us manage our Azure users, corporate users and we can even add users with x@.onmicrosoft.com emails. When we wanted to use Azure AD B2C for our consumers. So we have 2 choices to add our users which is a local user and an external user (Facebook, Google, etc) If the local user belongs to our corporate it is ok to create the user using the Azure AD B2C portal. But when we try to create

Getting Azure B2C SignUpSignIn Application Claims using MSAL in Xamarin.Forms

雨燕双飞 提交于 2019-11-28 05:30:20
问题 I'm creating a Xamarin.Forms app using Azure B2C and MSAL ( Microsoft.Identity.Client NuGet package) to authenticate users. When the app opens, I attempt to authenticate them in the background using the following code: AuthenticationResult ar; ar = await App.AuthenticationClient.AcquireTokenSilentAsync(Scopes, userIdentifier, Authority, SignUpSignInpolicy, false); If that fails, the app switches and authenticates them with the standard AquireTokenAsync() method. AuthenticationResult ar; ar =