docs: network hardening - #2654
Open
staaldraad wants to merge 1 commit into
Open
Conversation
External provider configuration must be flexible, however this does add some risk. Limiting the endpoints Auth can reach is best done at the infrastructure layer. Adds documentation calling this out.
xlgmokha
approved these changes
Jul 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Docs update
What is the current behavior?
External provider configuration must be flexible, however this does add some risk. Limiting the endpoints Auth can reach is best done at the infrastructure layer.
What is the new behavior?
Adds documentation calling out the need for network hardening.
Additional context
Auth is deliberately not prescriptive in the endpoints that can be configured. Self hosting Auth might mean you want SAML metadata to be fetched from an internal endpoint (localhost or RFC1918 network). The best protection for this is always at the network layer, it helps prevent DNS rebinding attacks, IP address encoding bypasses of allow lists etc.