Currently, deploying this app means that anyone with a Keycloak account can invite other users. Quoth the README:
There is no access granularity on the account creation implemented yet, so the accounts are "global"
It'd be handy if access to keycloak-collective-portal could be restricted to a sub-set of Keycloak users -- so that administrators could make and distribute invitation links, without throwing the doors completely open for 9,999 new accounts.
The simplest way of doing this that I can think of would be to add a config option for a specific username, or list of usernames, that's permitted to access. Even sweeter (although probably not necessary for now) would be the ability to require a Keycloak user to hold a specified role, or to be a member of a specified group.
Currently, deploying this app means that anyone with a Keycloak account can invite other users. Quoth the README:
> There is no access granularity on the account creation implemented yet, so the accounts are "global"
It'd be handy if access to `keycloak-collective-portal` could be restricted to a sub-set of Keycloak users -- so that administrators could make and distribute invitation links, without throwing the doors completely open for 9,999 new accounts.
The simplest way of doing this that I can think of would be to add a config option for a specific username, or list of usernames, that's permitted to access. Even sweeter (although probably not necessary for now) would be the ability to require a Keycloak user to hold a specified role, or to be a member of a specified group.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Currently, deploying this app means that anyone with a Keycloak account can invite other users. Quoth the README:
It'd be handy if access to
keycloak-collective-portalcould be restricted to a sub-set of Keycloak users -- so that administrators could make and distribute invitation links, without throwing the doors completely open for 9,999 new accounts.The simplest way of doing this that I can think of would be to add a config option for a specific username, or list of usernames, that's permitted to access. Even sweeter (although probably not necessary for now) would be the ability to require a Keycloak user to hold a specified role, or to be a member of a specified group.