jakartaee / jakartaee/authorization
TCK: Tests do not validate the PrincipalMapper at all
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 17
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
Current no TCK tests are making use of the PrincipalMapper API so there is no coverage of the function. This coverage could be contained by having overriding the Policy of PolicyFactory for one of the test and have it do things using the PrincipalMapper
Contributor guide
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 locating the TCK tests and the PrincipalMapper and PolicyFactory APIs. Add coverage that exercises PrincipalMapper through a test policy supplied by overriding the Policy of PolicyFactory, then run the relevant TCK tests and confirm the API behavior is validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authorization
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100