azure-ad-b2c

Azure B2C Sample Custom Policy, When SignIng In Shows 'Your password is incorrect'

泄露秘密 提交于 2021-01-27 19:07:37
问题 I have followed the Getting Started workflow here: https://docs.microsoft.com/azure/active-directory-b2c/active-directory-b2c-get-started-custom I followed it from scratch, twice, and have both times when trying to sign in with the sign-in & sign-up custom policy I am prompted with 'Your password is incorrect'. How can I properly authenticate? Things that are working: When I do signup the user journey completes, and the user is added to the directory Using built in policies I can sign in and

How to access two separate Web APIs protected using Azure AD B2C from a web app

此生再无相见时 提交于 2021-01-20 13:36:41
问题 We have two separeate dotnet core apis(API1 & API2) that are protected using azure ad b2c. Both these apis are registered on the b2c tenant and have their scopes exposed. We have a client web applicaiton that is to access the above protected apis. This web app has been registered as a applicaiton in b2c tenant and has api permissions set for the above apis with proper scopes defined. We use MSAL.net with a signinpolicy to sign the user in to the web app. the authentication call requires

How to access two separate Web APIs protected using Azure AD B2C from a web app

醉酒当歌 提交于 2021-01-20 13:34:54
问题 We have two separeate dotnet core apis(API1 & API2) that are protected using azure ad b2c. Both these apis are registered on the b2c tenant and have their scopes exposed. We have a client web applicaiton that is to access the above protected apis. This web app has been registered as a applicaiton in b2c tenant and has api permissions set for the above apis with proper scopes defined. We use MSAL.net with a signinpolicy to sign the user in to the web app. the authentication call requires

Bug identified in Azure B2C MFA phone number format (missing spaces)

和自甴很熟 提交于 2021-01-07 06:33:40
问题 This was suggested by Hari Krishna on another thread to open a new SO thread for this discussion. How do I programmatically clear or update a phone number for Azure AD B2C MFA? We are using B2C custom policies with a step to write back the user's MFA profile to the B2C profile. The B2C technical profile name is AAD-UserWritePhoneNumberUsingObjectId . <!-- Save MFA phone number: The precondition verifies whether the user provided a new number in the previous step. If so, then the phone number

Bug identified in Azure B2C MFA phone number format (missing spaces)

女生的网名这么多〃 提交于 2021-01-07 06:32:30
问题 This was suggested by Hari Krishna on another thread to open a new SO thread for this discussion. How do I programmatically clear or update a phone number for Azure AD B2C MFA? We are using B2C custom policies with a step to write back the user's MFA profile to the B2C profile. The B2C technical profile name is AAD-UserWritePhoneNumberUsingObjectId . <!-- Save MFA phone number: The precondition verifies whether the user provided a new number in the previous step. If so, then the phone number

Custom policy REST API ValidationTechnicalProfile ContinueOnError not working for HTTP codes like 404 NotFound and 401 unauthorized

北城余情 提交于 2021-01-05 11:06:53
问题 In Azure AD B2C custom policy, In a ValidationTechnicalProfile, while calling an external REST API, if the REST API returns HTTP error codes like 404 not found, or 401 unauthorized, the "ContinueOnError" attribute does not take effect. Instead the user journey ends abruptly throwing an error "Unable to validate the information provided" to the user interface in case of a self asserted technical profile. However the ContinueOnError attribute works as expected when the REST API returns error

Custom policy REST API ValidationTechnicalProfile ContinueOnError not working for HTTP codes like 404 NotFound and 401 unauthorized

跟風遠走 提交于 2021-01-05 11:06:44
问题 In Azure AD B2C custom policy, In a ValidationTechnicalProfile, while calling an external REST API, if the REST API returns HTTP error codes like 404 not found, or 401 unauthorized, the "ContinueOnError" attribute does not take effect. Instead the user journey ends abruptly throwing an error "Unable to validate the information provided" to the user interface in case of a self asserted technical profile. However the ContinueOnError attribute works as expected when the REST API returns error

Azure AD B2C: Policy IP Addresses to Allow Access to Custom Policy HTML Templates

本秂侑毒 提交于 2021-01-04 05:42:56
问题 We are using Azure AD B2C (still in preview) to authenticate customers to our application. We are going to use custom html templates for our sign-in experience and sign-up (gives us more power over format and links outside of MS content). Since our development environment is on a restricted network, the Systems Engineers would like to restrict access to those resources to a range or set of IP Addresses. We could just monitor traffic while we test, and then add those IPs we see, but it would

Sign in to ASP.Net Core Web Application -> API with Individual User Accounts using Azure AD B2C

泪湿孤枕 提交于 2021-01-01 10:04:18
问题 I have set up a Web Application with ASP.NET Razor Pages with -> Individual User Accounts -> Connect to an existing user store in the cloud (Azure AD B2C). This works really well and I could both sign up and sign in to the web application. However when I follow the guide for API I don't understand how to sign in. The example Controller /weatherforecast simply returns a HTTP 401 when the web application is started. Looking at the file structure I can't find any clues either but this could be

Azure AD ADFS gving Error “AADB2C90168: The HTTP-Redirect request does not contain the required parameter 'Signature' for a signed request.”

情到浓时终转凉″ 提交于 2020-12-31 06:21:26
问题 I am trying to use the following article to get ADFS working with Azure AD B2C in the start almost 3 weeks ago it worked and now I am getting this error. AzureAD B2C ADFS Configuration The Error I get after providing the credentials into ADFS. AADB2C90168: The HTTP-Redirect request does not contain the required parameter 'Signature' for a signed request. I removed my Custom policy and took on a vanilla policy from starter pack and configured ADFS but had the same result. There is no guidance