Overview
Making changes to the SAML/SSO configuration in the admin console may require you to restart your Jive application for the changes to apply.
Please see the table below for a complete list of SAML SSO configuration changes that will require a system restart:
Versions
Verified for versions: Jive 7 and Jive Cloud.
Information
|
Setting
|
Requires Restart?
|
|---|---|
| Base metadata URL | Yes (SP metadata changes) |
| Request Signed | Yes (SP metadata changes to indicate that the assertions will be signed) |
| IDP metadata | Yes |
| Logout URL | Yes |
| Passive Authentication | Yes |
| Sign Metadata | Yes |
| Key Store | Yes |
| User Attribute Mapping | No |
| Debug Mode | No |
| SSO Service Binding | No |
| Username Identity | No |
| Sync user profile on login | No |
| Maximum Authentication Age | No |
| Response Skew | No |
| Sign Assertions | No |
| Include Scoping | No |
| Proxy count | No |
| Enable Username Confirmation for New Users | No |
| Enable Email Confirmation for New Users | No |
| Enable Name Confirmation for New Users | No |
| Force Authentication | No |
| NameID Format | No |
| NameID Allow Create | No |
| Requested AuthnContext | No |
| Requested AuthnContext Comparison | No |
| RSA Signature Algorithm URI | No |
| Group Mapping Enabled | No |
| Enable disabled user account on login | No |
Comments
0 comments
Article is closed for comments.