Shibboleth with Kenexa BrassRing and ComponentsSpace

Cantor, Scott cantor.2 at osu.edu
Thu Aug 10 19:18:26 EDT 2017


On 8/10/17, 7:14 PM, "users on behalf of Hall, Gerry" <users-bounces at shibboleth.net on behalf of gerry.hall at emory.edu> wrote:

> The problem however is that the BrassRing service requires that the NameID attribute be returned in the SAML subject of the 
> xml assertion.  I believe that this is a shortcoming of the ComponentsSpace SAML implementation.

Whether it is or not, it's up to the service operator to set the requirements and decide what to accept. If they want to be like most vendors and make life difficult, then they will, whatever the implementation supports.

> can someone provide an example or point me towards any documentation that explains how to put the NameID attribute in the
> SAML subject instead of the SAML attribute statement?

There are no NameIDs in a SAML AttributeStatement by definition, a NameID is in the Subject. The documentation on generation of NameIDs is in the wiki.

-- Scott




More information about the users mailing list