Re: [cas-user] CAS 5.2 single sign out does not work for SAML 1.1 phpCAS clients

This shouldn't matter since cas 4.1.9 sends same request and SAME client, placed in same directory on the same server handles it correctly. >From phpCAS.log SAML REQUEST: @NOT_USED@ST-149-YAFlxnMQjDojiStFG4eN-cas.uek.krakow.pl [Client.php:1752] вторник, 24 апреля 2018 г., 19:09:17 UTC+2 польз

Re: [cas-user] CAS 5.2 single sign out does not work for SAML 1.1 phpCAS clients

Yes, and it releases attributes via saml with no issues. Only SLO doesn't work. вторник, 24 апреля 2018 г., 15:16:32 UTC+2 пользователь Manfredo Hopp написал: > > Do you have saml support dependency > > El martes, 24 de abril de 2018, Viacheslav Babanin > escribió: > >> It seems like I have

[cas-user] <>Re: CAS5.2.x Service registry json Error

<<>> But posting the fix I figured out, which might be helpful to someone. JSON formatting was not proper. It should have been [ { }, { } ] Thanks, Jay On Tuesday, April 24, 2018 at 11:21:25 PM UTC-5, Jay wrote: > > Hi All, > > I need a quick understanding

[cas-user] cas webflow maven dependency

not able to download org.apereo.cas cas-server-core-webflow ${cas.version} cas version is 5.2.4 -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.g

[cas-user] CAS5.2.x Service registry json Error

Hi All, I need a quick understanding on defining the entries in the ServiceRegistry json file. Below is the entry from my json file And see the below error i

[cas-user] mod_perl CAS authentication

I recently needed to integrate CAS authentication into a mod_perl based application; as I couldn't find anything that handled proxy authentication in a way that would work for me, I ended up implementing my own framework. I put it out on CPAN and github in case anyone else might find it useful:

[cas-user] Re: Problem integrating CAS 5.2.2 with WS Federation Identity Provider

> The error that I see in the logs: > ^[[33m WARN [org.apache.cxf.phase.PhaseInterceptorChain] - http://docs.oasis-open.org/ws-sx/ws-trust/200512/}SecurityTokenService#{http://docs.oasis-open.org/ws-sx/ws-trust/200512/}Issue has thrown exception, unwinding now>^[[m org.apache.cxf.interceptor.F

Re: [cas-user] CAS 5.2 single sign out does not work for SAML 1.1 phpCAS clients

from your log 2018-04-24 08:59:48,360 DEBUG [org.apereo.cas.logout.SamlCompliantLogoutMessageCreator] - @NOT_USED@ST-3-PppjmWz1yAHPFrZwFNMCRW5wsvI-v-cas-1]> its SAML2 whereas your client is SAML1 2018-04-24 7:27 GMT-03:00 Viacheslav Babanin : > It seems like I have a problem witch CAS 5.2.3 an

Re: [cas-user] CAS 5.2 single sign out does not work for SAML 1.1 phpCAS clients

Check your Apache access.log to see if the request is getting through. I see this when CAS sends logout request: 2018-04-24T09:32:57.816-07:00 lo...@z.comp.uvic.ca local2.notice httpd[2310]: access: coursespaces2d.uvic.ca: 111.104.118.193 - - [24/Apr/2018:09:32

Re: [cas-user] CAS 5.2 single sign out does not work for SAML 1.1 phpCAS clients

See https://github.com/apereo/cas/tree/5.2.x/core/cas-server-core-logout/src/main/java/org/apereo/cas/logout El martes, 24 de abril de 2018, Viacheslav Babanin escribió: > It seems like I have a problem witch CAS 5.2.3 and SAML logout requests. > Single logout doesn't work and from the logs

Re: [cas-user] CAS 5.2 single sign out does not work for SAML 1.1 phpCAS clients

Do you have saml support dependency El martes, 24 de abril de 2018, Viacheslav Babanin escribió: > It seems like I have a problem witch CAS 5.2.3 and SAML logout requests. > Single logout doesn't work and from the logs it seems like CAS constructs > SAML logout request but not actually sends it.

Re: [cas-user] Acceptable Usage Policy(AUP) in CAS5.2.x

Manually change login webflow xml. You will have to address missing credentials issue. El martes, 24 de abril de 2018, Jay escribió: > Hello everyone, > > As part of the migration from CAS3.5 to CAS5.2.x, we have to implement the > User Policy acceptance UI to allow the user to agree to the term

Re: [cas-user] CAS Logging {really log4j2 questions}

Hi All,     In case anyone else is wondering, it looks like there is a default 10MB size on the SizeBasedTriggeringPolicy (See https://github.com/apache/logging-log4j2/blob/master/log4j-core/src/main/java/org/apache/logging/log4j/core/appender/rolling/SizeBasedTriggeringPolicy.ja

Re: [cas-user] CAS Logging {really log4j2 questions}

Thanks, Duncan. I've got a pile of updates to make to the instructions, if I can ever get enough uninterrupted time to actually type them in. :-( I'll add that to the list. For what it's worth, I have our servers configured to send their logs to Graylog as well as the log files, and the TGTs are n

Re: [cas-user] CAS 5.2 single sign out does not work for SAML 1.1 phpCAS clients

It seems like I have a problem witch CAS 5.2.3 and SAML logout requests. Single logout doesn't work and from the logs it seems like CAS constructs SAML logout request but not actually sends it. I am using examplary phpCAS client from docs and when i go to ${cas-server}/cas/logout endpoint in th

[cas-user] Acceptable Usage Policy(AUP) in CAS5.2.x

Hello everyone, As part of the migration from CAS3.5 to CAS5.2.x, we have to implement the User Policy acceptance UI to allow the user to agree to the terms. In CAS3.5 we show the policy page even before the Login screen like shown below

Re: [cas-user] CAS 5.2 single sign out does not work for SAML 1.1 phpCAS clients

Ray, I have set handleLogoutRequests(true) and added those Loggers to CAS log4j2.xml, restarted CAS server in tomcat and nothing changes, and it seems in log like its publishing logout request but no details. That's exactyly what I did: 1. Added Loggers to CAS log4j2.xml 2. Restarted CAS in tom