Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No-new-users feature #46

Open
marcvs opened this issue Sep 2, 2022 · 1 comment
Open

No-new-users feature #46

marcvs opened this issue Sep 2, 2022 · 1 comment

Comments

@marcvs
Copy link
Collaborator

marcvs commented Sep 2, 2022

I have the feeling, that it may make sense to have a setting that allows some kind of "freeze" of users.

I.e. a mode in which users are not created automatically, and login only works if an account exists already.

I see the conflict with the authorized_users option in motley-cue.conf, but...

People may be afraid of a system that generates new accounts, and might prefer a mode in which they create a new account config. The only thing to set the correct "gecos" field for /etc/passwd, which can (more or less) easily be done with:

echo -n "${SUB}@${ISS}" | python -c "import sys; import urllib.parse; print(urllib.parse.quote_plus(str(sys.stdin.readlines()[0])))"
@dianagudu
Copy link
Owner

So something like the read_only mode for the LDAP backend, but applied to any backend? It probably makes sense then to move this issue to the feudalAdapter.

I don't see a big conflict with authorized_users, logically they are two separate things. Even when an account was created manually by the admin, the user needs to be authorised to access the service, either through authorized_users, authorized_vos, or by authorising all users from an OP. Sure, I guess there is redundant configuration, but that's the price to pay for the admin to gain more control.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants