AADB2C: Add multiply reply URLs with the same domain
If you create an Azure Active Directory B2C and then add an Application for your Web API, your Web API will only be able to receive tokens from a client that shares the same Application ID.
Currently, building a Web API that is accessed from several different clients is not supported.
This means that if you want to add different clients, you can configure them with the restriction that redirect URLs must all belong to the same domain.
I receive an error saying that the reply URLs are not in the same domain, see figure attached.
It is possible to add multiple reply URLs within the same domain, unfortunately the experience is a bit clunky and we’re working on fixing this.
At this time, in order to achieve this a setup with client1.domain.com and client2.domain.com as redirect URIs, you must first add the overarching domain as a redirect URI and then add the sub-domains, like so:
Check out this article for more info:
Aaron Johnson commented
still an issue I have multiple reply URLs specified it only works with the default selected. You can add a wildcard URL but you can't select it as the default reply URL making it useless.
Still not fixed for multiple domains (not sub-domains).
Any update on this issue
I'm seeing the exact same scenario as Rahul Sahay.
Please let me know, when this will be resolved.
Rahul Sahay commented
Mentioned URL is not working.
Also, in my case, I am registering app with application registration portal and there I am specifying set of reply urls. But, it is always taking the first one. Is there any way to get so that we can choose from the list like where we would like to redirect? say from consent screen itself.
I'm really hoping for wildcard support. This just doesn't make sense.
Wildcar support please!
Sujith Mathew Thomas commented
Is there any way to add more than 20 redirect urls? I have many customers with subdomains and I need my app to work in every subdomain. Currently im able to add it in only 20 subdomains
Is there any replacement for wildcard for reply URLs in B2C applications as we are developing a single page application contains different URLs. We can have wildcard(*) in reply URLs in Azure AD applications. Is there any concept like this in Azure B2C?
Eric Montgomery commented
I still see the exact same error, even adding one URL at a time. This is a major barrier to adoption
Jose Rojas commented
Neeraj Yadav commented
It was working fine earlier. I have a Preview tenant running successfully with multiple redirect Uris from same domain.
I created a new Production-scale tenant and now facing the same error. Seems this feature stops working in Production-scale tenant.
This is totally a show stopper. It's quite usual to have a single unified API instance catering multiple clients. Please enable it as soon as possible.
Cameron Bruce commented
Please fix. This is BASIC functionality that blocks A LOT of people.