Content
View differences
Updated by Wieland Lindenthal 7 days ago
### Steps to reproduce
1. On the cloud or an on-prem instance with Google, Azure or any other OpenID Connect provider configured
2. Create and activate enough users for the user limit to be reached
3. Disable self-registration in the authentication settings
4. Try signing in to the instance via OpenID Connect using an account that does not yet exist in OpenProject
### What is the buggy behavior?
* the user trying to sign in / register sees the following error
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/199445/content">
* and is prevented from registering
* \[WL: Wait, this is expected!\]
* admins will receive an email warning them that the user limit has been reached as follows:
> A new user (<email address>) tried to create an account on an OpenProject environment that you manage (<domain>). The user cannot activate their account since the user limit has been reached.
>
> To allow the user to sign in you can either:
>
> Upgrade your payment plan (here)
> Lock or delete an existing user (here)
### What is the expected behavior?
* This email should not be sent since the user would not have been able to activate their account irrespective of the user limit due to the disabled self-registration
* the user should see the following error instead (which they do see if the user limit has not been reached yet)
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/199444/content"></div></figure>
**OpenProject version**
_v14.5.1_
1. On the cloud or an on-prem instance with Google, Azure or any other OpenID Connect provider configured
2. Create and activate enough users for the user limit to be reached
3. Disable self-registration in the authentication settings
4. Try signing in to the instance via OpenID Connect using an account that does not yet exist in OpenProject
### What is the buggy behavior?
* the user trying to sign in / register sees the following error
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/199445/content">
* and is prevented from registering
* \[WL: Wait, this is expected!\]
> A new user (<email address>) tried to create an account on an OpenProject environment that you manage (<domain>). The user cannot activate their account since the user limit has been reached.
>
> To allow the user to sign in you can either:
>
> Upgrade your payment plan (here)
> Lock or delete an existing user (here)
### What is the expected behavior?
* This email should not be sent since the user would not have been able to activate their account irrespective of the user limit due to the disabled self-registration
* the user should see the following error instead (which they do see if the user limit has not been reached yet)
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/199444/content"></div></figure>
**OpenProject version**
_v14.5.1_