Thanks Neil, I appreciate it.
From: Neil Sabol [mailto:nssa...@unm.edu]
Sent: Thursday, October 29, 2015 10:23 AM
To: cas-user@lists.jasig.org
Subject: RE:[cas-user] logout
Good morning Chris,
I've used something like the following for logout with phpCAS:
require_once 'CAS.php';
phpCAS::client
On Thu, Oct 29, 2015 at 02:22:33PM +, Neil Sabol wrote:
> Good morning Chris,
>
> I've used something like the following for logout with phpCAS:
>
> require_once 'CAS.php';
> phpCAS::client(CAS_VERSION_2_0, 'your.cas.url', 443, 'yourcascontext');
> phpCAS::setNoCasServerValidation();
>
oning that detail and hope this helps,
-Neil
-Original Message-
From: Alberto Cabello Sánchez [mailto:albe...@unex.es]
Sent: Friday, October 30, 2015 7:42 AM
To: cas-user@lists.jasig.org
Subject: Re: [cas-user] logout
On Thu, Oct 29, 2015 at 02:22:33PM +, Neil Sabol wrote:
> Good
Good morning Chris,
I've used something like the following for logout with phpCAS:
require_once 'CAS.php';
phpCAS::client(CAS_VERSION_2_0, 'your.cas.url', 443, 'yourcascontext');
phpCAS::setNoCasServerValidation();
phpCAS::logout();
You would substitute your own CAS values for your.cas.url and
Never mind, I figured it out, we had someone wrote some code to customize that
behavior. Thanks, CAS does work as expected.
Yan
From: Misagh Moayyed [mailto:mmoay...@unicon.net]
Sent: Wednesday, September 30, 2015 1:53 AM
To: cas-user@lists.jasig.org
Subject: RE: [cas-user] logout redirect
I don't follow. Why or how is the .NET client sending your logout
requests?
From: Zhou, Yan [mailto:yan.x.z...@questdiagnostics.com]
Sent: Tuesday, September 29, 2015 7:45 AM
To: cas-user@lists.jasig.org
Subject: [cas-user] logout redirect not use "service" but "TARGET" for
.NET application?
Your logout url should receive a service parameter and that service
needs to be authorized in your registry. That should make it work.
From: Bryan Wooten [mailto:bryan.woo...@utah.edu]
Sent: Thursday, July 23, 2015 8:13 AM
To: cas-user@lists.jasig.org
Subject: [cas-user] Logout not following
That's what I thought, but the documentation
(https://wiki.jasig.org/display/CASC/phpCAS+logout), says that the
logout() method will kill the current PHP session. So that assumes they
application does not need to call session_destroy(). But if they do call
session_destroy() before the
@lists.jasig.orgmailto:cas-user@lists.jasig.org
Date: Thursday, February 19, 2015 at 11:05 AM
To: cas-user@lists.jasig.orgmailto:cas-user@lists.jasig.org
cas-user@lists.jasig.orgmailto:cas-user@lists.jasig.org
Subject: Re: [cas-user] Logout using phpCAS
Ben,
I have several PHP applications. The only way that I've
, February 19, 2015 10:12:45 AM
Subject: Re: [cas-user] Logout using phpCAS
That's what I thought, but the documentation
(https://wiki.jasig.org/display/CASC/phpCAS+logout), says that the
logout() method will kill the current PHP session. So that assumes they
application does not need to call
the redirect directly
in PHP.
Thanks,
Carl
- Original Message -
From: Benjamin Cherian benjamin.cher...@villanova.edu
To: cas-user@lists.jasig.org
Sent: Thursday, February 19, 2015 10:12:45 AM
Subject: Re: [cas-user] Logout using phpCAS
That's what I thought, but the documentation
(https
Ben,
Likely, you also have some kind of PHP session for the application.
= Generally speaking, logging out of CAS SSO does *NOT* log you out of any
application sessions. =
So you might want to clear any normal PHP session prior to calling
`phpCAS::logout()`.
Thanks,
Carl Waldbieser
ITS
My 3.5.2 CAS server is not following redirects on logout.
Do you have some evidence to share? Not much changed on HttpClient between
3.4.12 and 3.5.2 [1], other than adding the followServiceRedirects flag
which previously defaulted to true. Turn up org.jasig.cas.util to DEBUG and
see if you get
10:00 AM
To: cas-user@lists.jasig.org
Subject: Re: [cas-user] Logout view not following server url redirects
My 3.5.2 CAS server is not following redirects on logout.
Do you have some evidence to share? Not much changed on HttpClient between
3.4.12 and 3.5.2 [1], other than adding
Overlay this file in your configuration, and set true to false:
https://github.com/Jasig/cas/blob/4.0.x/cas-server-core/src/main/java/org/
jasig/cas/logout/LogoutManagerImpl.java#L144
Later versions of CAS will have an option to configure this via a
property. This will allow messages to be
Hi
Thanks for your replies. I tried both options, but as the logout parameter
on the application (Luminis) uses url rather than service, it doesn't work.
It looks like I will have to amend the casLogoutView.jsp, which is what
Ellucian have done with the bundled version of CAS.
Regards
David
and leave cas-servlet.xml untouched or is it telling me I need to modify
cas-servlet.xml and not cas.properties?
Leave cas-servlet.xml alone, and only change cas.properties.
From: David Kane [mailto:david.a.k...@ucd.ie]
Sent: Monday, May 19, 2014 8:45 AM
To: cas-user@lists.jasig.org
I am not sure about other possibilites, but it works for me when changing
|webapps/cas-server-webapp-3.5.2/WEB-INF/cas-servlet.xml
by setting |the attribute |followServiceRedirects| to |true|
HTH
Michael
Am 19.05.14 17:48, schrieb Misagh Moayyed:
and leave cas-servlet.xml untouched or is it
Anyone any hints on where it might go wrong?
Thanks!
Ralf
From: Steppacher Ralf [ralf.steppac...@derivativepartners.com]
Sent: Wednesday, October 09, 2013 16:42
To: cas-user@lists.jasig.org
Subject: [cas-user] Logout with mod_auth_cas not working
Hello CAS
Hi,
When you call the CAS logout (/cas/logout url), the CAS server will call all
the application service urls with a logout request.
It seems that you don't have the SSL certificate for an application in your CAS
server, which prevents the logout request to be send to the application.
Take a
right? Or I'm missing something?
Da: jleleu lel...@gmail.com
A: cas-user@lists.jasig.org
Inviato: Martedì 11 Settembre 2012 20:44
Oggetto: re:[cas-user] Logout with CAS\logout needs closing browser window
Hi,
I think that you also need to add
Thank you, Marvin.
--- On Sat, 2012/9/1, Marvin Addison marvin.addi...@gmail.com wrote:
On Fri, Aug 31, 2012 at 4:31 AM, s4...@yahoo.co.jp wrote:
I read that when I issue /logout command, it destroys the TGC that has
been stored by the CAS server upon establishment of a SSO session. I
Marvin, Scott
Would you please comment on it?
--- On Fri, 2012/8/31, s4...@yahoo.co.jp s4...@yahoo.co.jp wrote:
I read that when I issue /logout command, it destroys the TGC that has been
stored by the CAS server upon establishment of a SSO session. I assume the TGC
is stored on the client
On Fri, Aug 31, 2012 at 4:31 AM, s4...@yahoo.co.jp wrote:
I read that when I issue /logout command, it destroys the TGC that has
been stored by the CAS server upon establishment of a SSO session. I assume
the TGC is stored on the client side. But I also see that in CAS server
logs, something
@lists.jasig.org
Subject: Re: [cas-user] /logout service parameter
Its not an official part of the CAS protocol. It was included as service
when CAS3 was written (6 years ago) because it was a common extension. I
can't speak for why RubyCAS-client chose to use destination and not
service
as an
optionally supported parameter for /logout so when developers implement this
feature it is done consistently.
Any thoughts?
Jonathan
From: Scott Battaglia [scott.battag...@gmail.com]
Sent: Sunday, April 22, 2012 14:36
To: cas-user@lists.jasig.org
Subject: Re: [cas
Its not an official part of the CAS protocol. It was included as service
when CAS3 was written (6 years ago) because it was a common extension. I
can't speak for why RubyCAS-client chose to use destination and not
service.
Cheers,
Scott
On Mon, Apr 16, 2012 at 2:37 PM, Jonathan Windle
Folks,
We've CASsified Zimbra since 6.x and logout works without problems. As
andrew said in 2), When a user log out from zimbra, a simple html logout
page is displayed : this page is not on the same virtual host as zimbra
and I've verified that all zimbra related cookies got destroyed. This
Jon,
Merely changing a logout link in the UI to point to the CAS server logout URL
is, as you've discovered, insufficient where CAS's single logout callbacks
aren't implemented.
Rather, a Zimbra logout link should address a Zimbra server endpoint which
terminates the application-local
is there a way to logout to all casified apps in the
pop up windows once I logout to the main window?
Not sure what windows have to do with anything. They should all tie
back to a single CAS SSO session that maps to a single CASTGC cookie
on the client. So the normal single sign-out
Hi! I have my main window that is login
to CAS. From the main window, I have pop up windows that has links to different
casified applications.
My question is that, is there a way
to logout to all casified apps in the pop up windows once I logout to the
main window?
Thanks in advance.
-- You are
Which module of CAS you are using?
On May 12, 2011, at 1:38 PM, Jorge Infante Osorio jorg...@uci.cu wrote:
Hi all.
It´s possible that the logout action in all my applications protected by
CAS, after send me to the logout page of CAS automatically redirect me to
another page, for example
I´m using CAS for Liferay and a PHP application with phpCAS.
Jorge.
Ing. Jorge Infante Osorio.
J´Dpto Soluciones SOA.
CDAE.
UCI
-Mensaje original-
De: Vipin Jain [mailto:vjsat...@gmail.com]
Enviado el: jueves, 12 de mayo de 2011 13:56
Para: cas-user@lists.jasig.org
Asunto: Re: [cas-user
Hi Scott,
I'm not sure I actually understand what you mean. In my example, there
was no url to call back, as I was trying invoking the logout entrypoint
directly from the browser. The same however happens when I do logout
from an application (hence providing a callback url). I haven't said it
On Thu, Jan 21, 2010 at 4:43 AM, Giuseppe Sollazzo gsoll...@sgul.ac.ukwrote:
Hi Scott,
I'm not sure I actually understand what you mean. In my example, there was
no url to call back, as I was trying invoking the logout entrypoint directly
from the browser.
Yes, and as I've said the logout
Thanks, I'll give it a look.
G
Scott Battaglia wrote:
On Thu, Jan 21, 2010 at 4:43 AM, Giuseppe Sollazzo
gsoll...@sgul.ac.uk mailto:gsoll...@sgul.ac.uk wrote:
Hi Scott,
I'm not sure I actually understand what you mean. In my example,
there was no url to call back, as I was trying
What you're seeing is CAS trying to call back to your services to let them
know that the CAS session ended. One of the endpoints for your applications
has a certificate that disagrees with CAS :-)
On Wed, Jan 20, 2010 at 6:07 AM, Giuseppe Sollazzo gsoll...@sgul.ac.ukwrote:
Hi everyone,
I've
Maybe I'm missing something here so forgive my possibly stupid issue :-)
I'm actually calling the logout entrypoint directly from the browser, to
test it, entering https://myserver/cas-server-webapp-3.3.3/logout.
There's no application involved. Isn't it supposed to work anyway?
Giuseppe
On Wed, Jan 20, 2010 at 9:21 AM, Giuseppe Sollazzo gsoll...@sgul.ac.ukwrote:
Maybe I'm missing something here so forgive my possibly stupid issue :-)
I'm actually calling the logout entrypoint directly from the browser, to
test it, entering https://myserver/cas-server-webapp-3.3.3/logout.
A solution is to use the JPATicketRegistry and in an extra table
(users_logued) to store: user | TGT | date login | date logout
users_logued is updated in login, logout and ticket cleaner.
So if we want to logout an user from an external web application we can
select all the TGT of an user
Another solution is to store the user in the table ticketgrantingticket,
using JpaTicketRegistry.
How can I modify JpaTicketRegistry to achieve it ?
Diego Benedicto wrote:
A solution is to use the JPATicketRegistry and in an extra table
(users_logued) to store: user | TGT | date login |
This is also a feature I am looking for on my product's roadmap, so whatever
solution is identified, could someone please socialize the
design/implementation on the CAS wiki?
Thanks,
-Brian
From: Diego Benedicto [diego.benedi...@gmail.com]
Sent: Monday,
42 matches
Mail list logo
