<div dir="ltr"><span style="font-size:12.8000001907349px">Look at your IDP&#39;s logs (which are documented in the documentation).</span><br style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">Start with the audit log to determine what data (attributes and</span><br style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">NameIDs) have been sent to the SP.</span><br style="font-size:12.8000001907349px"><div><span style="font-size:12.8000001907349px">Then check your process log for any WARN or ERROR lines.</span></div><div>  </div><div>This time, i commented out the WebService dataconnector and use the following static attribute def and data connector along with the principal. here i am getting the static attribute at my SP side but principal is not coming but if i remove the static data connector and works with principalName attribute definition, principal is coming at SP side. I do not know what is going on here?</div><div><u><b>Attribute-resolver.xml</b></u></div><div><u><b><br></b></u></div><div><u><div>&lt;resolver:AttributeDefinition id=&quot;principal&quot; xsi:type=&quot;PrincipalName&quot; xmlns=&quot;urn:mace:shibboleth:2.0:resolver:ad&quot;&gt;</div><div><br></div><div>   &lt;resolver:AttributeEncoder xsi:type=&quot;enc:SAML2StringNameID&quot; /&gt;</div><div>    </div><div><span class="" style="white-space:pre">                </span>&lt;resolver:AttributeEncoder xsi:type=&quot;SAML2Base64&quot; xmlns=&quot;urn:mace:shibboleth:2.0:attribute:encoder&quot;</div><div>                                name=&quot;ORG_ATTRIBUTE_64&quot; /&gt;</div><div>  &lt;resolver:AttributeEncoder xsi:type=&quot;SAML2String&quot; xmlns=&quot;urn:mace:shibboleth:2.0:attribute:encoder&quot;</div><div>                                name=&quot;ORG_ATTRIBUTE&quot; /&gt;</div><div>&lt;/resolver:AttributeDefinition&gt;</div><div style="font-weight:bold"><br></div></u></div><div>&lt;resolver:AttributeDefinition id=&quot;SiteId&quot; xsi:type=&quot;ad:Simple&quot; xmlns=&quot;urn:mace:shibboleth:2.0:resolver:dc&quot;&gt; </div><div>    &lt;resolver:Dependency ref=&quot;staticAttributes&quot; /&gt; </div><div>    &lt;resolver:AttributeEncoder xsi:type=&quot;SAML2String&quot; xmlns=&quot;urn:mace:shibboleth:2.0:attribute:encoder&quot; name=&quot;SiteId&quot; friendlyName=&quot;SiteId&quot; /&gt; </div><div>    &lt;/resolver:AttributeDefinition&gt; </div><div>    </div><div>       &lt;resolver:DataConnector id=&quot;staticAttributes&quot; xsi:type=&quot;Static&quot; xmlns=&quot;urn:mace:shibboleth:2.0:resolver:dc&quot;&gt;</div><div>        &lt;Attribute id=&quot;SiteId&quot;&gt;</div><div>            &lt;Value&gt;${requestContext.principalName}&lt;/Value&gt;</div><div>        &lt;/Attribute&gt;</div><div>    &lt;/resolver:DataConnector&gt;</div><div><br></div><div>Shall i need to add the data connector for &#39;principal&#39; also? but why it is working if i did not add the  other attribute-def and data connector.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 15, 2014 at 5:36 PM, Peter Schober <span dir="ltr">&lt;<a href="mailto:peter.schober@univie.ac.at" target="_blank">peter.schober@univie.ac.at</a>&gt;</span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">* Surinaidu Majji &lt;<a href="mailto:pioneer.suri@gmail.com">pioneer.suri@gmail.com</a>&gt; [2014-12-15 10:05]:<br>
<span class="">&gt; Based on the suggestions given by many people i started doing changes in<br>
&gt; &quot;attribute-resolver.xml&quot;<br>
<br>
</span>Note that those also included posting questions about contributed<br>
extensions (i.e., the code you&#39;re trying to use) to the address stated<br>
next to the contribution in the wiki.<br>
<span class=""><br>
&gt; attributes at SP side. I added the following Restful webservice<br>
&gt; Dataconnector and attribute-definition to the attribute-resolver.xml.<br>
&gt;<br>
&gt; &lt;resolver:AttributeDefinition id=&quot;systemSettingData&quot; xsi:type=&quot;ad:Simple&quot;<br>
&gt; sourceAttributeID=&quot;systemSetting&quot;&gt;<br>
&gt;    &lt;resolver:Dependency ref=&quot;gws&quot; /&gt;<br>
&gt;    &lt;resolver:AttributeEncoder xsi:type=&quot;enc:SAML1String&quot;<br>
&gt; name=&quot;urn:mace:dir:attribute-def:systemSettingData&quot; /&gt;<br>
<br>
</span>That attribute name is not assigned by MACE-Dir. You can&#39;t just make<br>
up attributes in someone else&#39;s namespace.<br>
<span class=""><br>
&gt;    &lt;resolver:AttributeEncoder xsi:type=&quot;enc:SAML2String&quot;<br>
&gt; name=&quot;urn:oid:2.5.4.43&quot; friendlyName=&quot;systemSettingData&quot; /&gt;<br>
<br>
</span>And the OID 2.5.4.43 also doesn&#39;t mean &quot;systemSettingData&quot; (whatever<br>
that should be), it&#39;s defined by the ITU-T and ISO to mean &quot;initials&quot;<br>
of an individual&#39;s name. Cf. <a href="https://tools.ietf.org/html/rfc4519#section-2.14" target="_blank">https://tools.ietf.org/html/rfc4519#section-2.14</a><br>
<br>
If you want to define custom attributes you&#39;ll need to give them<br>
custom names in a namespace of your own (e.g. a http URL in a DNS<br>
domain you control).<br>
<span class=""><br>
&gt;  &lt;resolver:DataConnector xsi:type=&quot;WebService&quot; id=&quot;gws&quot;<br>
&gt; xmlns=&quot;urn:mace:washington.edu:idp:resolver:dc&quot;<br>
&gt;            authenticationType=&quot;NONE&quot;<br>
</span>[...]<br>
&gt;            username=&quot;user&quot;<br>
&gt;            password=&quot;pass&quot;&gt;<br>
<br>
Now, which one is it? No authentication to your web service, or some<br>
form of password-based authentication?<br>
<span class=""><br>
&gt;         &lt;QueryTemplate&gt;<br>
&gt;             &lt;![CDATA[<br>
&gt; group_sws/v1/search?member=${requestContext.principalName}&amp;type=effective]]&gt;<br>
&gt;         &lt;/QueryTemplate&gt;<br>
<br>
</span>That would only work if your web service looked and behaved exactly as<br>
the University of Washington&#39;s, of course. In other words, you&#39;ll need<br>
to change the QueryTemplate to match your web service&#39;s request URL.<br>
<span class=""><br>
&gt; Earlier we used to get principal(attributes) at SP side which have<br>
&gt; been set at the LoginHandler.Principal_Key(AuthenticationEngine).<br>
<br>
</span>No. The SP (which is not Shibboleth. so we cannot help with that) does<br>
not access the &quot;principal&quot; which is defined in the IDP. Instead, the<br>
IDP generates a SAML prototol message and sends it to the SP. There is<br>
no &quot;principal&quot; in the SAML, it does not leave the IDP.<br>
What and how you process the SAML on the SP is up to you. If your SAML<br>
SP implementation has the concet of a principal, that has nothing to<br>
do with the principal in the IDP.<br>
<br>
Of course Scott aready told you so, so writing this again here is<br>
probably moot.<br>
<span class=""><br>
&gt; After adding the additional above restful dataconector, i am even<br>
&gt; not getting the previous attribute(principal) at SP side. I know my<br>
&gt; restful dataconnector is not the exact one but i could not able to<br>
&gt; figure out what is the reason for not getting the &#39;principal&#39; also?<br>
<br>
</span>Look at your IDP&#39;s logs (which are documented in the documentation).<br>
Start with the audit log to determine what data (attributes and<br>
NameIDs) have been sent to the SP.<br>
Then check your process log for any WARN or ERROR lines.<br>
<span class="HOEnZb"><font color="#888888">-peter<br>
--<br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a><br>
</font></span></blockquote></div></div>