Hello
I thought I had my version 2 IDP working but it isn't. I seem to be releasing unscoped affiliations instead of scoped and I'm not sure what has gone wrong.
I'm using an SQL database to get the attributes / affiliations.
I thought I had it when I visited this page http://www.ukfederation.org.uk/content/Documents/Setup2IdP on the UK federation site where it talks about the eduPersonScopedAffiliation.
I thought it was because I had an attribute id of eduPersonAffiliation instead of eduPersonScopedAffiliation, but when I tried to fix that I ended up not releasing any affiliations rather than just unscoped.
I'm now back to where I started still releasing unscoped affiliations.
If anyone can point me in the right direction that would be fantastic.
This is what I have
<resolver:AttributeDefinition
id="eduPersonAffiliation"
xsi:type="Scoped"
xmlns="urn:mace:shibboleth:2.0:resolver:ad"
scope="myscope.ac.uk" sourceAttributeID="eduPersonAffiliation">
<resolver:Dependency ref="MyRef" />
<resolver:AttributeEncoder
xsi:type="SAML1String"
xmlns="urn:mace:shibboleth:2.0:attribute:encoder"
name="urn:mace:dir:attribute-def:eduPersonAffiliation" />
<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.1"
friendlyName="eduPersonAffiliation" />
</resolver:AttributeDefinition>
Like I said if I make the id eduPersonScopedAffiliation and match my data connectors and column mappings up I thought it would work, but it didn't, so clearly I've got a worse mess than I thought.
Thanks
Heather
|