Skip to content

Clarify caching behavior for SAMLAssertion destinations #2415

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
marikaner wants to merge 1 commit into
base: main
Choose a base branch
from
+5 −0
Open

Clarify caching behavior for SAMLAssertion destinations #2415

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
5 changes: 5 additions & 0 deletions docs-js/features/connectivity/destination-cache-isolation.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,11 @@ The destination cache holds destinations that potentially require HTTP requests,

Registered destinations and destinations from environment variables are not held in the destination cache.

:::note
Destinations with authentication type "SAMLAssertion" are never cached.
SAML assertions are only valid once and therefore should never be cached.
:::

### Cache Expiration

Destinations include authorization information and therefore should not be cached limitlessly.
Expand Down
Loading