Skip to content

Conversation

@quartje
Copy link

@quartje quartje commented Dec 6, 2025

In multi tenant environments it can be useful to use SAML group information for Kubernetes authorization purposes. This document describes how to implement this.

@talos-bot talos-bot moved this to In Review in Planning Dec 6, 2025
--auth-saml-label-rules='{"membership" : "groups" }'
```

This will extract value from the SAML attribute `memberhip` into the Omni user's identity resource label with the
Copy link
Member

Choose a reason for hiding this comment

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

memberhip?

Copy link
Author

Choose a reason for hiding this comment

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

To make it clear the the internal "groups" label is different from the external SAML attribute. In https://github.com/siderolabs/docs/blob/main/public/omni/security-and-authentication/using-saml-with-omni/configure-workspace-one-access-for-omni.mdx these two are the same, which is confusing.

Omni can extract SAML group information. For each group it will create a label on the identity in Omni.

Suppose you have your groups information in the SAML attribute "membership".
Start Omni with the following parameter:
Copy link
Member

Choose a reason for hiding this comment

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

what does it mean to "start with the following parameter"?

Copy link
Author

Choose a reason for hiding this comment

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

I've changed the terminology and it is now the same as on other pages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Review

Development

Successfully merging this pull request may close these issues.

2 participants