Adding separate note of security authentication schemes support in to 3.x.x release/migration docs.
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Description:
In APIM 2.6.0, when both mutual SSL and OAuth2 authentication schemes are selected, it allows the user to use either MTLS or OAuth2 to authenticate to the API. But, this behavior has been changed from 3.0.0 as now it is mandatory to enable either one of MTLS or OAuth2 when adding multiple auth schemes. So that, there is a difference between the way of supporting security auth schemes in APIM 2.6.0 and APIM 3.0.0. This change should be included into 3.x migration docs [1] and 3.0.0 release documents.
Suggested Labels:
Suggested Assignees:
Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:
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 with the linked 2.6.0-to-3.2.0 upgrade page and locate the 3.x migration documentation section covering multiple security authentication schemes. Check the 3.0.0 release documents as well; done means both explain the changed MTLS/OAuth2 behavior and the requirement to enable either scheme when multiple schemes are configured.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, authentication, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100