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.

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

Any impact on the client credentials flow? #46236

Closed
LXBdev opened this issue Jan 15, 2020 — with docs.microsoft.com · 2 comments
Closed

Any impact on the client credentials flow? #46236

LXBdev opened this issue Jan 15, 2020 — with docs.microsoft.com · 2 comments

Comments

Copy link

LXBdev commented Jan 15, 2020

See also https://stackoverflow.com/questions/59677741/actual-impact-of-deprecation-of-login-microsoftonline-com-for-b2c-tenants

New tenants created after this announcement will no longer be able to accept requests from login.microsoftonline.com.

My main concern is: How will this affect the client credentials grant? As far as I can see, this is only supported via login.microsoftonline.com.

Will the "Azure AD functionality" continue to work with login.microsoftonline.com indefinitely? If so, where can I draw the line of what this actually means?

I have created a new B2C tenant after the announcement. So far, everything works, even the B2C user flows via login.microsoftonline.com. The only difference at the moment is that I don't get the domain selection when I click on "run user flow".

My current understanding would be that "everything that uses B2C policies must use b2clogin.com" - everything else must continue to use login.microsoftonline.com.

Is this correct?


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@KrishnaG-MSFT
Copy link
Contributor

@LXBdev Thanks for your comment! We will review and provide an update as appropriate.

@amanmcse
Copy link
Contributor

@LXBdev Use of b2clogin.com is enforced for b2c functionality only. Client Credentials flow is not supported for B2C Applications. Since the App registered via App Registration under Azure AD B2C, can also be used for standard Azure AD as well which supports Client Credentials flow. For standard AAD functionality, use of b2clogin.com is not applicable and requires login.microsoftonline.com only.

For more details, refer to: https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-apps#daemonsserver-side-applications

Hope this helps clarifying your doubt.

I am proceeding with closure of this thread. Feel free to tag me in your reply if you have any further questions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants