|
| 1 | +--- |
| 2 | +sidebar_navigation: |
| 3 | + title: Settings |
| 4 | + priority: 990 |
| 5 | +description: Login and registration settings in OpenProject. |
| 6 | +keywords: authentication settings, login settings, registration settings, OpenProject login, login, registration |
| 7 | +--- |
| 8 | +# Login and registration |
| 9 | + |
| 10 | +To adapt general system **login and registration settings** in OpenProject, navigate to *Administration -> Authentication* and choose -> *Login and registration*. |
| 11 | + |
| 12 | +Here you can adapt various settings related to login and registration in OpenProject, grouped under three tabs: |
| 13 | + |
| 14 | +- Login and SSO |
| 15 | + |
| 16 | +- Registration |
| 17 | + |
| 18 | +- Passwords |
| 19 | + |
| 20 | + |
| 21 | + |
| 22 | +## Login and SSO settings |
| 23 | + |
| 24 | +Under the *Login and SSO* tab you can adjust following settings: |
| 25 | + |
| 26 | +1. Select a **direct login SSO provider**. If this option is active, login requests will be redirected to the configured Omniauth provider. This will disable the login dropdown and sign-in page. |
| 27 | + |
| 28 | + > [!NOTE] |
| 29 | + > |
| 30 | + > Unless you also disable password logins, with this option enabled, users can still log in internally by visiting internal login page, for example `https://yourinstancename.openproject.com/login/internal` login page. |
| 31 | +
|
| 32 | +2. Enable or disable the **autologin option**. This allows a user to remain logged in, even if they leave the site. If this option is activated, the “Stay signed in” option will appear on the login screen to be selected. |
| 33 | + |
| 34 | +3. Activate the **session expiration option**. |
| 35 | + |
| 36 | +4. Set the **duration for inactivity time**, after which a session will expire. Note that any value below 5 will be treated as disabling the session expiry setting. |
| 37 | + |
| 38 | +5. Define whether **user login, name, and mail address** should be logged for all requests. |
| 39 | + |
| 40 | +6. Define a path to **redirect users to after their first login**. If left empty, users are redirected to the homepage to see the onboarding tour. |
| 41 | + |
| 42 | +7. Set a **default path to redirect users to after login** (only if the login link is not a back link, i.e. `www.example.openproject.com/login`). If left empty, users are redirected to the homepage. |
| 43 | + |
| 44 | + Do not forget to **save** your changes. |
| 45 | + |
| 46 | + |
| 47 | + |
| 48 | +## Registration settings |
| 49 | + |
| 50 | +Under the *Registration* tab you can adjust following settings: |
| 51 | + |
| 52 | +1. Select if the **authentication is required** to access OpenProject. For versions 13.1 and higher of OpenProject, this setting will be checked by default |
| 53 | + |
| 54 | +> [!IMPORTANT] |
| 55 | +> If you uncheck this box, your OpenProject instance will be visible to the general public without logging in. The visibility of individual projects depends on [this setting](../../../user-guide/projects/#set-a-project-to-public). |
| 56 | +
|
| 57 | +2. Select an option for **self-registration**. Self-registration can either be **disabled**, or it can be allowed with the following criteria: |
| 58 | + |
| 59 | + a) **Account activation by email** - users can register on their own. They will receive an activation email and will need to activate their account after confirming their email address. |
| 60 | + |
| 61 | + > [!WARNING] |
| 62 | + > |
| 63 | + > Administrators have no moderation control over this activation process if this method is selected. |
| 64 | + |
| 65 | + b) **Manual account activation** - users can register on their own. However, an administrator (or a user with the global permission to create or manage users) needs to activate them. |
| 66 | + |
| 67 | + c) **Automatic account activation** - users can register on their own. Their accounts are immediately active without further action. |
| 68 | + |
| 69 | + > [!WARNING] |
| 70 | + > |
| 71 | + > Administrators have no moderation control over this activation process if this method is selected. |
| 72 | +
|
| 73 | +> [!NOTE] |
| 74 | +> By default, self-registration is only applied to internal users (logging in with username and password). If you have an identity provider such as LDAP, SAML or OpenID Connect, use the respective settings in their configuration to control which users are applicable for automatic user creation. |
| 75 | +
|
| 76 | +3. Define after how many days the **activation email sent to new users will expire**. Afterwards, you will have the possibility to [re-send the activation email](../../users-permissions/users/#resend-user-invitation-via-email) via the user settings. |
| 77 | + |
| 78 | +3. Choose for which **language** you want to define **the footer displayed at the bottom of the registration page** and formulate that footer text. |
| 79 | + |
| 80 | + |
| 81 | + |
| 82 | + |
| 83 | +## Password settings |
| 84 | + |
| 85 | +Under the *Password* tab you can adjust following settings: |
| 86 | + |
| 87 | +1. Define the **minimum password length**. |
| 88 | +2. Select what **character classes are a mandatory part of the password**. |
| 89 | +3. Define the **minimum number of required character classes**. |
| 90 | +4. Define the number of days, after which a **password change should be enforced**. Value of 0 disables this option, i.e. no password change will be enforced. |
| 91 | +5. Define the **number of the most recently used passwords that a user should not be allowed to reuse**. |
| 92 | +6. Activate the **password reset** (Forgot your password option). This way users will be able to reset their own passwords via email. |
| 93 | +7. Define the number of failed **login attempts, after which a user will be temporarily blocked**. Value of 0 disables this option, i.e. users will not be blocked after any amount of failed login attempts. |
| 94 | +8. Define the **duration of the time, for which the user will be blocked after failed login attempts**. Value of 0 disables this option. |
| 95 | + |
| 96 | + |
| 97 | + |
0 commit comments