What exactly are you trying to accomplish?
I want Cas to be:
- authentication source
- source of some attributes (for example name)
Honestly, I think using
CAS as an authentication provider for Shib, as discussed in
https://wiki.jasig.org/display/CASUM/Shibboleth-CAS+Integration, is
the ideal integration path. We're quite happy with this approach.
This way is OK for me, but one thing is missing: CAS2.0 protocol does
not transport attributes. So we are using SAML. And the problem is that
Shib does not validate correctly using samlValidate.
Michal Pysz
Do you know any solution for this problem?
Maybe I'll have some suggestions after I understand what you're trying
to do exactly.
M
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
