I've been attempting to wire up Azure Container App Service (ACA) with my B2C tenant and have run across an issue. ACA provides out of the box auth mechanisms for multiple identity providers including OIDC, AAD, Google, Apple etc. However, the callback url convention they've adopted requires a certain format, namely like so: https://.....xyz/.auth/login/aad/callback. What I've discovered through painful trial and error is that BC2 doesn't like the '.' in the callback url and when the case arises it falls back to a default callback url and simply ignores the user provided url. So, then the '/.auth ends getting overwritten with 'azure-ad-b2c'. Is this intentional and can it be overridden or addressed in some fashion?
BC89
commented
1 year ago
Greetings,
I've been attempting to wire up Azure Container App Service (ACA) with my B2C tenant and have run across an issue. ACA provides out of the box auth mechanisms for multiple identity providers including OIDC, AAD, Google, Apple etc. However, the callback url convention they've adopted requires a certain format, namely like so: https://.....xyz/.auth/login/aad/callback. What I've discovered through painful trial and error is that BC2 doesn't like the '.' in the callback url and when the case arises it falls back to a default callback url and simply ignores the user provided url. So, then the '/.auth ends getting overwritten with 'azure-ad-b2c'. Is this intentional and can it be overridden or addressed in some fashion?
Thx!