Bitwarden_rs: Disabling Signups not working for me

[Zuwizara]

Subject of the issue

Signups are still possible after disabling it via Environment and/or admin interface. I tried both Environment-var and the admin interface, always restarted the container after disabling, however im still able to create sign up new user on the Login Page. Could someone verify if this is a problem in my deployment or a bug?

Your environment

• Bitwarden_rs version: 1.13.1-632d5526
• Install method: Docker (using Compose in Portainer)
• Clients used: WebVault
• Reverse proxy and version: Traefik 1.7
• Version of mysql/postgresql: i use the includede database
• Other relevant information:

Steps to reproduce

Disable Signup in Admin Interface or via Environment Var, restart the server and sign up with a new email.

Expected behaviour

Signups not possible after disabling them

Actual behaviour

Signups are still possible

Relevant logs

Please tell me which logs i should provide since i do not see anything relevant in the logs i see from the container in portainer.

[bergernetch]

Same problem here, same bitwarden_rs version, disabling via env var does not work. It does show up as disabled in the admin interface.

[Latschenharry]

Have you tried creating an account. Because the register button will always be there. If signups are disabled, you will only get an error when hitting the sent button.

[Zuwizara]

Have you tried creating an account. Because the register button will always be there. If signups are disabled, you will only get an error when hitting the sent button.

Yes, i always created test users and it was successful

[mprasil]

Submitted a PR to hopefully fix this.

[bergernetch]

Have you tried creating an account. Because the register button will always be there. If signups are disabled, you will only get an error when hitting the sent button.

Yes, i always created test users and it was successful

Same here. I would like it when the create button would also be disabled or even better removed.

[dani-garcia]

This should be fixed now, sorry about that!