[Documentation] Add differnt ways of using keycloak security
- Dominant language
- Java
- Stars
- 7
- Forks
- 5
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 33
Description
### Relevant documentation
Other
### Problem description (optional)
The Keycloak and Spring security can be used in different ways, depending on what is needed. We need to document the different ways
### Desired solution
add the following concepts to the documentation for keycloak security:
- roles
- use-case roles
- application roles
### Additional context (optional)
- Internal discussion: https://git.muenchen.de/ccse/Architekt_innenrunde/-/issues/161
### No duplicate
- [x] I confirm that this issue is not a duplicate
### Code of Conduct
- [x] I agree to follow this project's Code of Conduct
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the existing Keycloak and Spring Security documentation and the linked internal discussion, issue 161. Document the roles, use-case roles, and application roles, clearly explaining the different ways of using Keycloak security; done means all three requested concepts are covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- authentication, authorization, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100