Hi Milt,
Thank you for the information. I've configured it now. It was <property
name="allowedAttributes"> missed out in the servicedao bean. Now I'm able to
retrieve the attributes from the database.
Thanks and Regards,Basith
On Tuesday, December 16, 2014 5:42 AM, Milt Epstein
<[email protected]> wrote:
What are you using as your CAS client? mod_auth_cas, by chance?
IIRC, I was getting a similar error when I didn't have:
CASValidateSaml On
in my apache/mod_auth_cas config.
If you're not using mod_auth_cas, perhaps there's some similar config
that's missing for the client you are using, that specifies that
you're doing SAML validation, and hence sends the appropriate
parameters to the CAS server on the validation call.
Milt Epstein
Applications Developer
Graduate School of Library and Information Science (GSLIS)
University of Illinois at Urbana-Champaign (UIUC)
[email protected]
On Mon, 15 Dec 2014, Abdul Basith S wrote:
> Dear Support,
> I've configured the SAML integration with CAS 4.0 and deployed it as per the
> link https://wiki.jasig.org/display/CASUM/SAML+Support+in+CAS+4.
> But when I checked the response from browser using /samlValidate its throwing
> 'service' and 'ticket' parameters are both required as status message.
> Can you please help me to fix this issue immediately ?
> Thanks and Regards,
> Basith
>
> --
> 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
--
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
--
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
