Skip to content

SAML limitation: need for restart with multiple nodes #11444

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Karuna-Mendix wants to merge 1 commit into
base: development
Choose a base branch
from
Open

SAML limitation: need for restart with multiple nodes #11444

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion ...place/platform-supported-content/modules/SAML/saml-installaion-configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -278,7 +278,11 @@ The following settings apply to the IdP configuration:

* **Log SAML Requests** – Determines whether all requests and login attempts should be logged and stored in an entity.

When you add a new configuration or change an existing one, you should restart your app. This ensures that the correct configuration is used.
In versions below 4.1.0, when you add a new configuration or change an existing one, you must restart your app. This ensures that the correct configuration is used by all instances of your app. From version 4.1.0, a restart is no longer required after changing the configuration.

{{% alert color="info" %}}
In a horizontally-scaled environment, configuration changes made on one instance are not automatically propagated to other instances. To apply changes consistently across all instances, you must restart all instances of your app.
{{% /alert %}}

## IdP Configuration

Expand Down
Loading