Repository navigation
Replies: 1 comment 2 replies
|
Yes, this is true. Some research brought me to the implementation of the docker protocol. It seems there is only the "Allow All" mapper implemented. => You are right: For now you can only use KeyCloak for authentication but not for implementing scope based filtering (as documented here). |
|
Hi @krombel I exactly had the same issue with the docker registry authentication. So I ended up writing my own mapper. I use Keycloak 21 and registry 2.8.2. My mapper is configurative by environment variables and you can group users according to their email domain, roles and groups. |
|
@alexanderwolz Looks very promising, i'll take a look and see if it solves my issues. |
Uh oh!
There was an error while loading. Please reload this page.
Its pretty hard to read from the documentation
But, I can't find anything regarding setting up scope mappings so I can limit access to the registry, there is only one mapper, Docker Auth Mapper with a setting of Allow All, and no obvious way of limiting anything.
Has anyone gotten this to work, or can KeyCloak only be used for authentication against a docker registry?
All reactions