Azure Function - Authentication - Allowed External Redirect URLs

Question

I have added acudose://easyauth.callback and https://www.microsoft.com. Only https://www.microsoft.com works. Using the post_login_redirect_url parameter sends me to the done page instead of acudose://easyauth.callback when providing the acudose://easyback.callback, but the post_login_redirect_url parameter of https://www.microsoft.com works just fine. I got through the oauth and redirect just fine to https://www.microsoft.com. This was literally working 24 hours ago. With no change to the authentication configuration. Troubleshooting complains that I don't have it configured. Additionally, at some point acudose://auth stopped working. It said that's not a valid URI. I am guessing Microsoft changed their validation as that's based on their own documentation. I honestly considering using a different service as this is ridiculous. It's no wonder Microsoft no longer calls this EasyAuth.

Answer 1

Hi,

the error is very clear. azure's easyauth is now rejecting your acudose://easyauth.callback url because it has suddenly decided it is not a valid format for a redirect uri. this is likely due to a recent backend validation change microsoft rolled out, even if their own docs suggested this format.

the protocol acudose:// is a custom scheme, and it seems the new validation is being overly strict, probably only allowing proper http or https urls.

here is what u can try right now. instead of the protocol format, try using a deep link style with a fake https prefix. sometimes this tricks the validator.

try adding this to your allowed redirect urls. https://acudose.easyauth.callback

this is a common workaround for custom schemes. it might just be enough to get past the validation check while still allowing your app to intercept it.

if that does not work, u might need to temporarily use a real https endpoint as an intermediary. set up a very simple web page that just redirects to acudose://easyauth.callback. then, in your azure function, set the post_login_redirect_url to this new https endpoint. it is an extra hop, but it could unblock u.

also, please please please open a support ticket with azure. provide them with the exact error and your configuration. they need to know they broke a working setup with a silent validation change.

really hope u find a workaround. being at the mercy of a silent platform change is the worst.

Best regards,

Alex

and "yes" if you would follow me at Q&A - personaly thx.
P.S. If my answer help to you, please Accept my answer

https://ctrlaltdel.blog/