|
| [WB] - CAS SSO & samlvalidate |
| Iniciado por guest, 04,oct. 2016 17:50 - 3 respuestas |
| |
| | | |
|
| |
| Publicado el 04,octubre 2016 - 17:50 |
we have implemented CAS SSO in one of our clients using httprequest and
https://cas_server/serviceValidate…=http://my_app&ticket=xxxxxxx and works without problems.
Now another client told us that we must use SAML instead.
We can't find out how should it be implemented, probably using samlvalidate instead of servicevalidate but if we try only with that change the CAS server always returns one error.
Anyone have done it and how?
Thanks |
| |
| |
| | | |
|
| | |
| |
| Publicado el 04,octubre 2016 - 21:19 |
Paulo,
I had an IIS Server running an asp.net app (not WxDev) a while back that was using a CAS 2.0 server for authentication. The customer then upgraded to a CAS 4.0 server, and we had to make the following change on the client side:
change
ticketValidatorName=Cas20
to
ticketValidatorName=Saml11
Reference:
http://shermandigital.com/blog/integrate-cas-with-aspnet-applications/
May not help at all, but just in case...
...jack |
| |
| |
| | | |
|
| | |
| |
| Publicado el 06,octubre 2016 - 10:35 |
Thanks Jack,
Our goal is to use CAS sso without any CAS client, it's easy with the CAS protocol but we can't find out how to do it using SAML protocol. |
| |
| |
| | | |
|
| | |
| |
| Publicado el 07,octubre 2016 - 10:38 |
If you use the CAS protocol it works with HTTPREQUEST (GET) for the SAML protocol use HTTPREQUEST (POST)
For the the SAML protocol the URL is something like:
https://cas_server/samlValidate…
If you use the CAS protocol the parameters are service and ticket
If you use the SAML protocol the parameters are TARGET and SAMLart |
| |
| |
| | | |
|
| | | | |
| | |
|