Skip to content

Add option to configure blockNewUsers #8906

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

Closed
Tracked by #9072
mrsimonemms opened this issue Mar 20, 2022 · 2 comments · Fixed by #9718
Closed
Tracked by #9072

Add option to configure blockNewUsers #8906

mrsimonemms opened this issue Mar 20, 2022 · 2 comments · Fixed by #9718
Assignees
Labels
team: delivery Issue belongs to the self-hosted team

Comments

@mrsimonemms
Copy link
Contributor

When creating a Gitpod instance, it would make sense to prevent users from being able to sign up to that instance. As many users will be enterprises with a specific domain name, this should be considered an easy win

Config to allow gitpod.io users to login

blockNewUsers:
  enabled: true
  passlist: 
    - gitpod.io
@csweichel
Copy link
Contributor

can we please start adding those things to experimental config? It looks like we're inflating the installer config surface without need.

@mrsimonemms
Copy link
Contributor Author

mrsimonemms commented Mar 21, 2022

This is already in the Installer config block and has been ever since the first iteration you did back in August. This ticket is to add this config to KOTS

This shouldn't go into the experimental block as this is something that self-hosted admins use and require

@mrsimonemms mrsimonemms added the team: delivery Issue belongs to the self-hosted team label May 3, 2022
@mrsimonemms mrsimonemms self-assigned this May 3, 2022
Repository owner moved this from 📓Scheduled to ✨Done in 🚚 Security, Infrastructure, and Delivery Team (SID) May 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team: delivery Issue belongs to the self-hosted team
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

2 participants