Releasing attribute to SP's with 2 different source dependencies
Lipscomb, Gary
glipscomb at csu.edu.au
Tue Nov 29 17:06:03 EST 2016
Hi all,
We are currently upgrading from idpv2 to idpv3 and in the process are cleaning up some of the legacy non-standard use of attributes. Our SP's have been notified of the changes and have had over 12 months to make the changes. As usual there is one who hasn't and won't be able to by the date we wish to go live. We are also simplifying our LDAP instances and removing our customised schema definitions as well.
In our v2 we defined EPPN as (not following the definition)
<resolver:AttributeDefinition id="eduPersonPrincipalName" xsi:type="Simple" xmlns="urn:mace:shibboleth:2.0:resolver:ad"
sourceAttributeID="csuPartyId">
<resolver:Dependency ref="ldap" />
<resolver:DisplayName xml:lang="en">Global Username (EPPN)</resolver:DisplayName>
<resolver:AttributeEncoder xsi:type="SAML1String" xmlns="urn:mace:shibboleth:2.0:attribute:encoder"
name="urn:mace:dir:attribute-def:eduPersonPrincipalName" />
<resolver:AttributeEncoder xsi:type="SAML2String" xmlns="urn:mace:shibboleth:2.0:attribute:encoder"
name="urn:oid:1.3.6.1.4.1.5923.1.1.1.6" friendlyName="eduPersonPrincipalName" />
</resolver:AttributeDefinition>
We replaced this with another attribute schacPersonalUniqueID and released this as well to the appropriate SP's so they could make the necessary code changes. Not done by this particular SP.
In v3 we are still releasing schacPersonalUniqueID as well as a corrected version of EPPN
<AttributeDefinition xsi:type="Scoped"
id="eduPersonPrincipalName"
scope="%{idp.scope}"
sourceAttributeID="uid">
<Dependency ref="uid" />
<DisplayName xml:lang="en">Principal Name (ePPN)</DisplayName>
<AttributeEncoder xsi:type="SAML1ScopedString" name="urn:mace:dir:attribute-def:eduPersonPrincipalName"/>
<AttributeEncoder xsi:type="SAML2ScopedString" name="urn:oid:1.3.6.1.4.1.5923.1.1.1.6" friendlyName="eduPersonPrincipalName"/>
</AttributeDefinition>
Is it possible to release the v2 EPPN attribute to only one SP with the same ID?
Do you just give it another name but use the same encoder definitions? Would this work as shown below?
<resolver:AttributeDefinition id="EPPN-CSUpartyID" xsi:type="Simple" xmlns="urn:mace:shibboleth:2.0:resolver:ad"
sourceAttributeID="csuPartyId">
<resolver:Dependency ref="ldap" />
<resolver:DisplayName xml:lang="en">Global Username (EPPN)</resolver:DisplayName>
<resolver:AttributeEncoder xsi:type="SAML1String" xmlns="urn:mace:shibboleth:2.0:attribute:encoder"
name="urn:mace:dir:attribute-def:eduPersonPrincipalName" />
<resolver:AttributeEncoder xsi:type="SAML2String" xmlns="urn:mace:shibboleth:2.0:attribute:encoder"
name="urn:oid:1.3.6.1.4.1.5923.1.1.1.6" friendlyName="eduPersonPrincipalName" />
</resolver:AttributeDefinition>
Regards
Gary
| ALBURY-WODONGA | BATHURST | CANBERRA | DUBBO | GOULBURN | MELBOURNE | ONTARIO | ORANGE | PORT MACQUARIE | SYDNEY | WAGGA WAGGA |
LEGAL NOTICE
This email (and any attachment) is confidential and is intended for the use of the addressee(s) only. If you are not the intended recipient of this email, you must not copy, distribute, take any action in reliance on it or disclose it to anyone. Any confidentiality is not waived or lost by reason of mistaken delivery. Email should be checked for viruses and defects before opening. Charles Sturt University (CSU) does not accept liability for viruses or any consequence which arise as a result of this email transmission. Email communications with CSU may be subject to automated email filtering, which could result in the delay or deletion of a legitimate email before it is read at CSU. The views expressed in this email are not necessarily those of CSU.
Charles Sturt University in Australia The Grange Chancellery, Panorama Avenue, Bathurst NSW Australia 2795 (ABN: 83 878 708 551; CRICOS Provider Number: 00005F (National)). TEQSA Provider Number: PV12018
Charles Sturt University in Ontario 860 Harrington Court, Burlington Ontario Canada L7N 3N4 Registration: peqab.ca.
Consider the environment before printing this email.
More information about the users
mailing list