EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics
  3. Hot-Reload Authentication Mode, Trust Relationship, Library Cookie Settings, and SSO Configuration Without Library Server Restart

Hot-Reload Authentication Mode, Trust Relationship, Library Cookie Settings, and SSO Configuration Without Library Server Restart

Strategy (June 2026) adds Library support for faster runtime updates for authentication-related settings. This update reduces operational overhead and helps administrators make common authentication changes with less disruption.

The Strategy (June 2026) update include the following four important no-restart improvements:

  • Authentication mode updates can now be applied without restarting the Library server in supported scenarios. Supported authentication modes includes Standard, LDAP, SAML, OIDC, Guest, Trusted, and JWT.
  • Trust relationship updates no longer require you to restart the Library server.
  • SSO configuration updates can be hot-reloaded for both server-level and application-level settings when updated using Workstation.
  • Cookie setting updates can also take effect without restarting Library when it is updated through the supported configuration paths.

How Changes are Applied

configOverride.properties Changes

For supported settings in configOverride.properties, changes can take effect without restarting the Library server.

This update applies to authentication mode switching enhancements, trust relationship, and cookie related runtime behavior.

Note: Hot-reload is supported. If you update the relevant supported settings in configOverride.properties, it will take effect automatically after the reload cycle.

SSO Configuration Changes

SSO configuration behaves differently from the general supported configOverride.properties updates.

  • If SSO configuration is updated using Workstation, the change can be hot-reloaded.
  • If SSO configuration files are edited directly, you must restart the Library server for the change to take effect.

Important: Directly editing SSO configuration files does not provide the same hot-reload behavior as updating SSO configuration using Workstation.

Change type

Change location

Restart required?

Expected behavior

Authentication mode

Supported UI/API or configOverride.properties

No

Change is applied through runtime reload

Trust relationship

Supported management workflow

No

Library uses the updated trust relationship without restart

Cookie setting

Supported configuration path or configOveride.properties

No

Supported cookie settings are applied through runtime reload

SSO configuration

Workstation UI

No

Change is hot-reloaded

SSO configuration

Direct file edit

Yes

Restart is required before the new SSO configuration takes effect


Comment

0 comments

Details

Knowledge Article

Published:

June 8, 2026

Last Updated:

June 18, 2026