subject-id as a computedID help
Satya Mohapatra
patra at mit.edu
Wed Jan 15 23:13:57 EST 2020
Hi,
I am trying to implement the new subject-id as a computedID.
Here is the relevant snippet from attribute-resolver.xml of the IdP.
<!-- Deprecated persistent NameID wrapped in a deprecated SAML Attribute value -->
<resolver:AttributeDefinition id="subject-id" xsi:type="ad:Scoped" scope=“test.org" sourceAttributeID="computedID">
<resolver:Dependency ref="computedID" />
<resolver:AttributeEncoder xsi:type="enc:SAML2ScopedString" name="urn:oasis:names:tc:SAML:attribute:subject-id" friendlyName="subject-id" encodeType="false" />
</resolver:AttributeDefinition>
<resolver:DataConnector id="computedID" xsi:type="ComputedId" xmlns="urn:mace:shibboleth:2.0:resolver:dc" generatedAttributeID="computedID" sourceAttributeID="employeeNumber" salt="%{idp.persistentId.salt}">
<resolver:Dependency ref=“LDAP" />
</resolver:DataConnector>
At the SP, I am seeing the attribute is being removed.
WARN Shibboleth.AttributeFilter [1] [default]: removed value at position (0) of attribute (subject-id) from (https://login-test.ligo.org/idp/shibboleth)
WARN Shibboleth.AttributeFilter [1] [default]: no values left, removing attribute (subject-id) from (https://login-test.ligo.org/idp/shibboleth)
The attribute map at the SP has the following:
<Attribute name="urn:oasis:names:tc:SAML:attribute:subject-id" id="subject-id”/>
Any suggestion what I could be doing wrong ?
Thanks,
---
Satya Mohapatra | ସତ୍ୟ ମହାପାତ୍ର | सत्य महापात्र | ستیا موہپترا
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1885 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/users/attachments/20200116/fc2f699d/attachment.p7s>
More information about the users
mailing list