<div dir="ltr">Hello,<div><br></div><div>I'm currently implementing Shibboleth at our institution using the Unicon Shib-CAS authentication plugin (<a href="https://github.com/Unicon/shib-cas-authn2">https://github.com/Unicon/shib-cas-authn2</a>) to defer authentication to our existing CAS deployment. Currently, our CAS also retrieves attributes from LDAP.</div>
<div><br></div><div>I was wondering how to get the attributes that have already been retrieved by CAS over to Shib for release? I know I can just set up an LDAP data connector with the appropriate attribute definitions on the Shib side, but then we have 2 LDAP lookups for the same principal... one on the CAS side and one on the Shib side. I'm sure there's not too much of a performance hit using this method, but out of curiosity, I'd like to see if there's a way to avoid this.</div>
<div><br></div><div>Some previous searches let me to the general idea of storing assertion.getAttributes() in the LoginHandler.SUBJECT_KEY in the AuthenticatedNameTranslator class. I also need to create a Data Connector to pull these attributes back out, but this is where I'm getting lost.</div>
<div><br></div><div>Any suggestions? Am I on the right track here? I'm still very new to Shibboleth so pardon any ignorance.</div><div><br></div><div>Thank you!<br clear="all"><div><br></div>-- <br><div dir="ltr"><b>Tadeusz Sacilowski</b><div>
<i>Manager, Portal & Mobile Development</i></div><div>Teachers College, Columbia University</div><div><a href="mailto:sacilowski@tc.columbia.edu" target="_blank">sacilowski@tc.columbia.edu</a></div></div>
</div></div>