The CAS 2 protocol itself doesn't support attributes so its either a local modification or you need to be able to parse SAML1.1 responses.
-Scott -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia On Tue, Sep 23, 2008 at 7:57 AM, Joram Barrez <[EMAIL PROTECTED]>wrote: > While strolling the Jira, I found this bug: > http://www.ja-sig.org/issues/browse/CAS-655 > > Is this still correct: do we need to change the jsp ourself te have > attributes? > > > Joram > > > On Tue, Sep 23, 2008 at 10:00 AM, Joram Barrez <[EMAIL PROTECTED]>wrote: > >> Hi list, >> >> I'm currently setting up a CAS server with an LDAP backend. This >> configuration works perfect. >> >> Now I'm looking into returning some attributes (eg. email, surname, etc) >> to the client. The attributeRepository is correctly configured and the LDAP >> attributes are correctly placed into a map (I see 'Flattend map ...' with >> the correct values in cas.log. These attributes are not in the XML response >> I get from /serviceValidate >> But, when strolling through the source code I see that >> "casServiceValidationSuccess.jsp", which is rendered to the success XML >> response does not contain attributes ... so this makes me believe that there >> is no way of getting the attributes ... >> >> Any guidance what I'm doing wrong here? >> >> >> >> >> Joram >> > > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > >
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
