After 31 August 2022, will not be supported for Azure AD B2C. The new endpoint minimizes Microsoft branding within the URL and offers seamless redirect authentication. But it seems a lot of hassle and an unnecessary indirection, which I want to avoid as much as possible. We recommend you start using as the redirect URL for apps connecting to Azure AD B2C by that date. Navigate to the Azure Active Directory login page on Input user credentials Sign in and redirect back to the demo application Cache. Another idea is to have the Single Page App send the login request to my own server as AJAX request and then that server performs the login on behalf of that user and then relay back the token to the Single Page App. I went through the documentation and found one can customize the login page (in User Flow Policies/Page Layout), but it seems it will still be a separate page, which I don't want. What I want is to have the login control embedded in the Single Page App. The problem is the login page opens in a separate window with the B2C Url in the address bar. The scenario is user login in the Azure B2C, gets the token & the use the token to call Azure function. Register your Bizagi Work Portal as an authorized app in your Azure AD. Test API & Single Page app are registered as proper application in the Azure B2C & the setup is working properly. To configure Bizagi to sign in with Azure AD, please follow these steps: 1. I also have an Azure B2C & a Test api (as an Azure Function) created. I am working with Azure AD B2C sample and for testing purpose I am using a slightly modified Single page app sample.
0 kommentar(er)
