microsoft / microsoft/azure-container-apps
Azure B2C OIDC - callback url
Nobody has claimed this yet.
- Dominant language
- Bicep
- Stars
- 445
- Forks
- 54
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 3
Description
Greetings,
I've been attempting to wire up Azure Container App Service (ACA) with my Azure 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 ges overwritten with 'azure-ad-b2c'. I know this isn't necessarily an ACA issue but can the callback convention be overwritten because the MS folks in the B2C group don't seem all that active so I'm looking for work arounds.
Thx!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing Azure Container Apps' documented OIDC callback configuration and the Azure B2C callback URL behavior described in the issue. Determine whether the callback convention can be overridden or whether a supported workaround exists; document the confirmed configuration or limitation as the outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- authentication, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100