postiz-app
postiz-app copied to clipboard
Disable User Regsitration
🔖 Feature description
Please add an ENV-Variable called "USER_REGISTRATION" that we can set to "false" to disable new users from creating accounts
🎤 Why is this feature needed ?
Public Instances can be abused without this feature
✌️ How do you aim to achieve this?
Add an ENV-Variable called "USER_REGISTRATION" that we can set to "false" to disable new users from creating accounts
🔄️ Additional Information
No response
👀 Have you spent some time to check if this feature request has been raised before?
- [X] I checked and didn't find similar issue
Are you willing to submit PR?
None
@nevo-david I can handle that if you want.
@nevo-david I can handle that if you want.
That would be great!
For the time being: I'm using this in my NGINX reverse proxy config, maybe it can be of help for someone: # Redirect /auth/ to /auth/login location = /auth/ { return 301 https://subdomain.domain.com/auth/login; } location = /auth { return 301 https://subdomain.domain.com/auth/login; }
# Block /api/auth/register
location = /api/auth/register {
return 403;
}
location = /api/auth/register/ {
return 403;
}
I prefer to take this kind direction. https://docs.nginx.com/nginx/admin-guide/security-controls/configuring-http-basic-authentication/
Is there any change that for time being we can just add simple DOCKER env variable that indicate registration is disabled ?
Has been implemented.
@egelhaus is it implemented as proposed (Please add an ENV-Variable called "USER_REGISTRATION" that we can set to "false" to disable new users from creating accounts)? Thanks in advance.
I'm having trouble with this one. After disabling the registration, I cannot use Google SSO for login.
I'm having trouble with this one. After disabling the registration, I cannot use Google SSO for login.
Yes, as Google SSO would be for production use, and Zhe feature is only for development / testing purposes, it can be used for production, but them you won't have SSO.