You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
For some SAML-backed deployments, it is useful to be able to allow or deny login based on the value of a SAML attribute.
For example, consider a system where SAML users are divided into "staff" and "customers". The organisation wishes only staff to have access to the Matrix server. The SAML server might return the following in the SAML assertion:
The SAML handler should inspect the userGroup attribute and check that it matches staff. Obviously, the attribute name and value need to be configurable.
I suggest that we implement this in the core SamlHandler rather than the SamlMappingProvider. I'd suggest configuration options like:
For some SAML-backed deployments, it is useful to be able to allow or deny login based on the value of a SAML attribute.
For example, consider a system where SAML users are divided into "staff" and "customers". The organisation wishes only staff to have access to the Matrix server. The SAML server might return the following in the SAML assertion:
The SAML handler should inspect the
userGroup
attribute and check that it matchesstaff
. Obviously, the attribute name and value need to be configurable.I suggest that we implement this in the core
SamlHandler
rather than theSamlMappingProvider
. I'd suggest configuration options like:(which leaves the route open in future to specifying a type of match such as
contains
or (regex)matches
).The text was updated successfully, but these errors were encountered: