Using value maps for RBAC
Robert.Duncan at ncirl.ie
Wed Nov 7 07:23:12 EST 2018
The fine documentation provides the following example:
<AttributeDefinition id="mapped" xsi:type="Mapped">
<InputAttributeDefinition ref="uid" />
<AttributeEncoder xsi:type="SAML2String" name="https://example.org/example/name" friendlyName="Mapped" encodeType="false" />
but my question was:
Is there a way to use multiple source attributes in a value map? not multiple source values
From: users <users-bounces at shibboleth.net> on behalf of Peter Schober <peter.schober at univie.ac.at>
Sent: Wednesday 7 November 2018 11:57:23
To: users at shibboleth.net
Subject: Re: Using value maps for RBAC
* Robert Duncan <Robert.Duncan at ncirl.ie> [2018-11-07 12:05]:
> Is there a way to use multiple source attributes in a value map?
> I want to map roles to departments but I also want to map certain
> individuals to special roles,
You can also have multiple ValueMap elements within the same Mapped
The fine documentation covers all of that, cf. "Cardinality":
(Easily found by entering "Mapped" in the search filed in the upper right.)
The example below also demonstrates that.
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
The information contained and transmitted in this e-mail is confidential information, and is intended only for the named recipient to which it is addressed. The content of this e-mail may not have been sent with the authority of National College of Ireland. Any views or opinions presented are solely those of the author and do not necessarily represent those of National College of Ireland. If the reader of this message is not the named recipient or a person responsible for delivering it to the named recipient, you are notified that the review, dissemination, distribution, transmission, printing or copying, forwarding, or any other use of this message or any part of it, including any attachments, is strictly prohibited. If you have received this communication in error, please delete the e-mail and destroy all record of this communication. Thank you for your assistance.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users