RE: [cas-user] Hazelcast management console

Curl always worked for me as standard browser, when it came to the cookie mgmt. See http://curl.haxx.se/docs/http-cookies.html „Netscape once created a file format for storing cookies on disk so that they would survive browser restarts. curl adopted that file format to allow sharing the cookies

Re: [cas-user] CAS SLO for Rails and JAVA application

The path is basically to scope the TGC domain to my domain with path set to root. When a user logs in via cas, and is redirected to my app, I can setup a session, using the values of the TGC cookie and on each subsequent request, I can check the value in the current sessions against the TGC coo

RE: [cas-user] CAS SLO for Rails and JAVA application

That’s the file. I’d have to know what you changed and why before I can recommend a path. From: James Naadjie [mailto:jnaad...@aps.org] Sent: Thursday, January 14, 2016 12:46 PM To: CAS Community Cc: mmoay...@unicon.net Subject: Re: [cas-user] CAS SLO for Rails and JAVA application Thanks f

[cas-user] CAS 4.1.3 with logback logging backend instead of log4j2

Hello, I am attempting to get CAS 4.1.3 running with logging through logback but am having difficulty. As far as I can tell since cas-server-core has included org.slf4j.impl.StaticLoggerBinder to intercept and sanitize logs (pull request adding feature )

Re: [cas-user] CAS SLO for Rails and JAVA application

Thanks for the answers and pointing me in the right direction. Follow up question. Would it be possible to change the TGC cookie domain and path? I have tried changing the ticketGrantingTicketCookieGenerator.xml configuration for the cookie, but the path doesn't change. On Thursday, Januar

RE: [cas-user] CAS SLO for Rails and JAVA application

Start with this: https://jasig.github.io/cas/4.1.x/installation/Logout-Single-Signout.html Also on the theory/context of SLO: https://wiki.shibboleth.net/confluence/display/CONCEPT/SLOIssues 1. SLO is enabled by default in CAS. 2. No special config is needed, unless you need it

Re: [cas-user] Re: CAS Intermittent SSO logins issues

Juan, I always start with Get everything into the log, then focus on things of interest. e.g Ray On Thu, 2016-01-14 at 15:03 +, Juan Quintanilla wrote: Hi, thanks for your response. We are using tomcat for the session replication and

Re: [cas-user] Hazelcast management console

> On Jan 14, 2016, at 8:13 AM, Misagh Moayyed wrote: > [>] They do. See https://github.com/Jasig/cas/milestones > CAS 4.2 RC1 has been out for a couple of weeks now. The GA release timeline > will depend on community feedback and progress of tests. > > In short, monthly patch cycles. 3-month mi

[cas-user] CAS SLO for Rails and JAVA application

I’m not very clear on how Single Log out works with CAS server 4.1 and hope for a clear and simple explanation to help resolve an issue i’m having with my client applications. Currently SSO works fine with my two applications. Users can login to application A,B and C, A and B are Ruby on R

RE: [cas-user] Hazelcast management console

Likely not. You no longer get the full TGT in the logs. Since the TGC is scoped to the browser, I am not sure I fully understand what that curl command actually does without you having access to that browser. From: cas-user@apereo.org [mailto:cas-user@apereo.org] On Behalf Of Tom Mendenhall S

Re: [cas-user] Hazelcast management console

Can we script a kill session CAS 4.2 like we are able to do in 3.n? Can we still read the TGT in the catalina.out/cas.log file? curl -s --cookie "CASTGC=TGT-n-xyzzy-node" https://cas.domain.edu/cas/logout On Wed, Jan 13, 2016 at 10:43 PM, Misagh Moayyed wrote: > > In general, how might on

RE: [cas-user] Hazelcast management console

> Understandably, the CAS roadmaps ave no expected release dates for future > versions. For planning purposes, when might a production-worthy 4.2 be > available? Order of magnitude would be fine: a year, six months, longer > than > XX, [>] They do. See https://github.com/Jasig/cas/milestones

Re: [cas-user] Hazelcast management console

> On Jan 13, 2016, at 10:43 PM, Misagh Moayyed wrote: > >> In general, how might one administratively kill a CAS session in CAS 4.x? > > [>] Only possible in 4.2 and beyond. You log into the SSO Sessions > dashboard, find the session you want and you kill it with a click of a > button. Under

Re: [cas-user] Re: CAS Intermittent SSO logins issues

Hi, thanks for your response. We are using tomcat for the session replication and all the Tickets are stored Oracle Db which both CAS servers access. When we have encountered the issue the user hits the same CAS Server during all the login attempts because of the sticky sessions. Its happened

Re: [cas-user] Re: CAS Intermittent SSO logins issues

Out of curiosity, what happens if you take the load balancer out of the picture - does the required re-authentication happen? Also, do you have any kind of session replication set up between your CAS nodes, such as hazelcast? Also, what frequency does this happen? Eg., if someone logs into a CAS

[cas-user] Re: CAS Intermittent SSO logins issues

So wanted to send an update, it seems that the intermittent SSO issue also happened on our Second CAS server today. Once it was rebooted it seemed to not prompt the user to log in again to a CAS application once they had already authenticated to another CAS application. Below is a snippet from

Re: [cas-user] CAS with Ajax on timed out ticket

Were you able to add this header to the CAS Server with configuration or did you have to customize the source? On Thursday, January 14, 2016 at 2:54:22 AM UTC-5, jacques-emmanuel.babarit wrote: > > Hello, > > i had the same issue, what i did is add a specific header to every request > coming fr