Shibboleth with Kenexa BrassRing and ComponentsSpace

[Hall, Gerry]

ShibUsers,
I have a service, IBM Kennexa BrassRing, that uses another service, ComponentsSpace, to implement SAML SSO.  The requirements for this service include 3 custom attributes Application, SiteId and NameID.  I have been able to add each of these attributes to my IdP’s attribute resolver and each of the attributes are being returned to the BrassRing service as expected in the SAML attribute statement of the SAML assertion.

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.  However, to ensure that I have exhausted all possibilities, I am wondering if anyone can comment as to whether this is indeed a shortcoming of the ComponentSpace SAML as I suspect, or, if not, 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?  Hope this makes sense, but see below as to what I mean.

For example, within the SAML assertion, the NameID appears as below (where kpal is the value of the NameID attribute).
<saml:Subject>
<saml:NameID>kpal</saml:NameID>
</saml:Subject>

For example, within the SAML assertion, the Attributes appear as below.
<saml:AttributeStatement>
<saml:Attribute Name="Application" FriendlyName="Application">
<saml:AttributeValue>1</saml:AttributeValue>
</saml:Attribute>
<saml:Attribute Name="SiteId" FriendlyName="SiteId">
<saml:AttributeValue>0</saml:AttributeValue>
</saml:Attribute>
</saml:AttributeStatement>




________________________________

This e-mail message (including any attachments) is for the sole use of
the intended recipient(s) and may contain confidential and privileged
information. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution
or copying of this message (including any attachments) is strictly
prohibited.

If you have received this message in error, please contact
the sender by reply e-mail message and destroy all copies of the
original message (including attachments).