You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: install-and-configure/install-on-prem-platform/advanced-configuration.md
+11-12
Original file line number
Diff line number
Diff line change
@@ -6,8 +6,7 @@ navTitle: Advanced Configuration
6
6
# Configuration Options
7
7
8
8
{% hint style="info" %}
9
-
This part of the documentation is only intended in the context of a supported PoC (Proof of Concept) together with the Steadybit team.
10
-
Please, [book an appointment](https://www.steadybit.com/book-demo) to scope your PoC before continuing to evaluate the on-prem solution.
9
+
This part of the documentation is only intended in the context of a supported PoC (Proof of Concept) together with the Steadybit team. Please, [book an appointment](https://www.steadybit.com/book-demo) to scope your PoC before continuing to evaluate the on-prem solution.
11
10
12
11
If you just want to try out Steadybit, we recommend you [sign up for our SaaS platform](https://signup.steadybit.com).
13
12
{% endhint %}
@@ -57,15 +56,15 @@ For running the platform with multiple instances, a Redis message broker is requ
|`STEADYBIT_WEB_PUBLIC_URL`|| URL to point to your Steadybit installation. Use this if your platform is running behind a reverse proxy doing path rewriting. Also it is used for the links in notifications. |
62
61
|`STEADYBIT_WEB_PUBLIC_EXPERIMENT_PORT`|| By default the Websocket connections are advertised to the agents on port 7878. If the public port differs (e.g. because of a proxy) use this property to advertise a different port. |
63
62
|`STEADYBIT_WEB_PUBLIC_EXPERIMENT_URL`|| By default the Websocket connections are advertised on the same url name as the agents registers to. If you run a separate loadbalancer for the websockets you can override the advertised url. |
|`LOGGING_FORMAT`|| By default Steadybit uses `text` format. Set this this to `json` to switch the log format to JSON. |
70
69
71
70
### Static-Authentication
@@ -98,16 +97,16 @@ By default the ldap is accessed anonymously, unless `STEADYBIT_AUTH_LDAP_MANAGER
98
97
|`STEADYBIT_AUTH_LDAP_SYNC_TEAM_SEARCH_FILTER`|| <p>The filter for the groupOfNames/groupOfUniqueNames for the teams<br><strong>Example:</strong> <code>ou=teams,ou=groups,dc=steadybit,dc=com</code></p> |
99
98
|`STEADYBIT_AUTH_LDAP_SYNC_TEAM_KEY_ATTRIBUTE`|| <p>The attribute to use as Team key<br><strong>Example:</strong> <code>cn=steadybit_admin,ou=groups,dc=steadybit,dc=com</code></p> |
100
99
|`STEADYBIT_AUTH_LDAP_SYNC_TEAM_NAME_ATTRIBUTE`|| <p>The attribute to use as Team name<br><strong>Example:</strong> <code>cn=steadybit_admin,ou=groups,dc=steadybit,dc=com</code></p> |
101
-
|`STEADYBIT_AUTH_SYNC_CRON`|| <p>Cron Expression which defines the periods for the LDAP synchronization<br><strong>Default:</strong> <code>0 0 _/2 ? _ \*\*</code></p> |
100
+
|`STEADYBIT_AUTH_SYNC_CRON`|| <p>Cron Expression which defines the periods for the LDAP synchronization<br><strong>Default:</strong> <code>0 0 _/2 ? _ * *</code></p>|
102
101
103
102
### OpenID-Connect Authentication
104
103
105
-
You can use an OpenID Connect compatible authentication provider for user authentication. Steadybit uses the `authorization_code` grant type.
104
+
You can use an OpenID Connect compatible authentication provider for user authentication. Steadybit uses the `authorization_code` grant type. The callback URL is `https://<host>/oauth2/login/code/default`
106
105
107
106
> The first user to login will be assigned the `ADMIN` role, all other will be assigned the `USER` role. The roles can be changed by an admin user via the UI.
0 commit comments