Skip to content

Conversation

@mrogala-sauce
Copy link
Contributor

Support for using Kerberos SPNEGO headers to be injected into proxied connections.

How this works:

  • user configures Kerberos KDC server connection (using regular krb5.conf file and usertab)
  • user configures a list of web hosts that are known to require Kerberos SPNEGO authorization header
  • for each forwarded connection, kerberos adapter fetches Kerberos ticket for particular host (if needed), converts to SPNEGO format and injects into request header (tickets are cached internally).
  • both host and upstream proxy Kerberos auth is supported (using either Authorization or Proxy-Authorization header).

Copy link
Contributor

@markamsauce markamsauce left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. One minor comment for doc but can be ignored if no other changes planned to this PR.

To create a custom keytab/keytab entry run:

```
root@rogal:/etc/krb5kdc# ktutil
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe it's better to clean examples from any "private names" and put root@host:/etc/krb5kdc# ktutil or jus root:/etc/krb5kdc # ktutil.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good point, changed

@mrogala-sauce mrogala-sauce merged commit 725029c into main Dec 12, 2025
5 of 7 checks passed
@mrogala-sauce mrogala-sauce deleted the kerberos-implementation branch December 12, 2025 13:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants