Hi,
Can you try enabled debug log:
https://apereo.github.io/cas/5.3.x/installation/Troubleshooting-Guide.html#review-logs
And capture more logs for debugging purpose?
Also, please be careful when reading the documentation, I see that you are
using CAS 5.3.x, but you are viewing CAS 5.2.x
I have successfully configured the CAS 5.3.10 overlay to delegate
authentication to a SAML IDP and I can successfully authenticate with the
IDP using the CAS login page default CASTEST button provided
(https://test1./cas/login), However, after authentication is
successful, I am redirected to
I have successfully configured the CAS 5.3.10 overlay to delegate
authentication to a SAML IDP and I can successfully authenticate with the
IDP using the CAS login page default CASTEST button provided
(https://test1./cas/login), However, after authentication is
successful, I am redirected to
Hi all,
I am not familiar with CAS 3, however, I have done some research and tried
building CAS 6.1.1 (latest release CAS) with OneLogin PHPSAML,
And I found that, CAS 6 can successfully integrate with OneLogin PHPSaml
using SAML protocol. No error for CAS 6.
So, maybe the lack of base64
No problem glad it helps! - Andy
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS
Folks,
I see that the mod_auth_cas module for Apache2 does not support
consumption/use of Proxy Ticket'ed Validation.
Anyone stumble across a solution along these lines. I'd like to Proxy
Authenticate from a Web Application to a resource behind a reverse proxy
that is not a browser front
Yeah, I think that should work. I've done it once or twice for a web
application. You'll have to bring in the CAS Servlet filter to do it. Pretty
much everything of mine is using Apache Shiro for security, so I'm not very
familiar with the servlet based security constraints.
Unfortunatly, I never got resolution on this.
Here is my ticket for the OneLogin PHP-SAML lib:
https://github.com/onelogin/php-saml/issues/390
OneLogin quoted this from the SAML spec:
3.5.4 Message Encoding
Messages are encoded for use with this binding by encoding the XML into an HTML
form
I have been running into this same issue for quite a while now. Have not
been able to identify the source.
On Thu, Nov 21, 2019 at 11:25 AM Chris G wrote:
> I'm just wondering if anyone figured this out. I have the same issue--SAML
> Responses from CAS are NOT base64 encoded, but all the
I'm just wondering if anyone figured this out. I have the same issue--SAML
Responses from CAS are NOT base64 encoded, but all the clients I have seem
to expect the SAML Response to be base64 encoded.
Is this a SAML spec, that it should be base64 encoded and CAS isn't
implementing it properly?
Hello Mister Andy .
thank you very much for taking the time to give me such a complete answer.
I now have a better understanding of how to integrate O365.
The little explanatory diagram is perfect!
This week, I understood how the connection to O365 worked, and why the
rememberME can't remember
11 matches
Mail list logo
