Mar 13 2018
- last edited on
Jan 14 2022
I have an Angular 5 app which is authenticated using Azure AD using AdalJs. The whole app is protected by azure ad and user needs to be logged in to be able to access any page.
Now in my Azure Ad app I have added reply url as "https://app.domain.com".
In a fresh session User hits https://app.domain.com and gets authenticated by azure ad and returns to the web site.
In a fresh session User hits https://app.domain.com/page1 and gets authenticated by Azure AD and Azure AD does not return the user back to my website with an error "https://app.domain.com/page1 " is not registered as a reply url in the Azure AD app.
Now if I go to my Azure AD app and make the reply URL as a wildcard URL like "https://app.domain.com/*" then the redirection flow after authentication works perfectly for all pages inside my website.
I see this is one blog about this method
So is the wildcard URL approach in reply URL safe to be used? The blog above says there is some security concerns but I cannot find out what those concerns are?
Also, is the wildcard URL approach the correct approach here?
Dec 22 2018 12:54 AM - edited Dec 22 2018 12:59 AM
Were you able to find a way to supply wildcard reply URLs? In the new App registrations page, it is not possible to add wildcards, so I guess this is not really supported.
Update: I kept searching and found this:
4.1.5. Threat: Open Redirectors on Client
An open redirector is an endpoint using a parameter to automatically redirect a user agent to the location specified by the parameter value without any validation. If the authorization server allows the client to register only part of the redirect URI, an attacker can use an open redirector operated by the client to construct a redirect URI that will pass the authorization server validation but will send the authorization "code" or access token to an endpoint under the control of the attacker.
Impact: An attacker could gain access to authorization "codes" or access tokens.
o Require clients to register full redirect URI (Section 126.96.36.199)."
Feb 04 2020 08:05 AM
using oauth2 protocol this is not possible because the authentication request cannot be signed. But this could be possible using SAML protocol if AZure AD would implement the feature to validate the signature of the saml request, in this way the client app could change runtime the value of assertion consumer url contained in the saml request.