Hi,
It's quite some time since we talked about embedded login forms.
The flow stops at CAS login : you mean it ends up with the viewLoginForm
view state ?
I think there is a problem when trying to resume the webflow to submit
credentials.
So can you turn on DEBUG logs on
I’m testing the CASification of Jaspersoft Server 4.7 and keep getting this
Exception “java.security.cert.CertificateException: No subject names
present”
It's likely because the FQDN of your CAS server host is different from
the CN of the cert used to secure Tomcat. Testing either a CAS
We are looking to make this an Highly Available
CAS implementation currently and I’ve noticed that a great deal of progress
seems to have been made in this area since the release of 3.5 and the
implementation of EhCache.
I'd agree with that assessment.
With this said, I’m curious how
bean id=samlServiceTicketUniqueIdGenerator
class=org.jasig.cas.util.SamlCompliantUniqueTicketIdGenerator
constructor-arg index=0 value=https://localhost:${host.port.https}; /
property name=saml2compliant value=true /
/bean
My questions is about the constructor value.
We have a
hello,
Once again there is something i don't understand in the expiration policy.
To test it, i configure the ticketExpirationPolicies.xml like this :
bean id=serviceTicketExpirationPolicy
class=org.jasig.cas.ticket.support.HardTimeoutExpirationPolicy
c:timeToKillInMilliSeconds=5000/
Ok i have a clue,
Since my application not throw a session timeout, cas client will not
reauthenticate the user?
I configured 1min timeout for my client application and 2min in
HardTimeoutExpirationPolicy
if each minute I press F5, i'm reauthenticated automatically (a new ST is
created), but
One small follow-up to this...
With 3.5.X, do we still need a separate DB instance in order for us to use the
web-based Service Manager or does EhCache take over this role as well?
Ben Branch
UNIX/Linux Administrator
University of Central Oklahoma
ITIL Foundation v3, Network+, RHCSA
100 N.
With 3.5.X, do we still need a separate DB instance in order for us to use
the web-based Service Manager or does EhCache take over this role as well?
I don't believe there's a ServiceRegistryDao implementation that uses
EhCache, so no. Though I don't imagine it would be too difficult to
Alright folks, here's where I'm at with CAS 3.4.11:
I've got Tomcat clustering functioning well over multicast. I can see in the
logs the two instances hitting each other and the java sessions are replicating
I tried the jboss.jgroups ticket replication and once I finally beat that into
Just adding a side note, that you might be interested in maintaining the
list of registered services using a JSON flat file:
https://github.com/Unicon/cas-addons/wiki/Configuring-JSON-Services-Regist
ry
...and on top of that, add support for change events and automatic
reloading of services :)
Hi Misagh.
The login for the test user is in testuser in the svn repo.
Regarding LPPE - We discussed our potential need for LPPE and will leave it as
a second phase item to explore. Our existing mechanisms for disabling and
expiring accounts occurs in our identity management system which
On Thu, 23 Aug 2012, Marvin Addison wrote:
bean id=samlServiceTicketUniqueIdGenerator
class=org.jasig.cas.util.SamlCompliantUniqueTicketIdGenerator
constructor-arg index=0 value=https://localhost:${host.port.https}; /
property name=saml2compliant value=true /
/bean
My questions is
thx for this explanation. I haven't found a wiki page that explain the
basics .. I missed somethig ?
Le jeudi 23 août 2012 20:18:31 UTC+2, Jérôme LELEU a écrit :
Hi,
You have two sessions : your web application session and the SSO session.
As long as your web app session lasts, the CAS
Some additional links for your review:
CAS protocol:
http://www.jasig.org/cas/protocol
CAS Ticket Expiration Policy:
https://wiki.jasig.org/display/CASUM/Ticket+Expiration+Policy
-Misagh
From: Nicolas Geraud [mailto:nicolas.ger...@gmail.com]
Sent: Thursday, August 23, 2012 12:01 PM
14 matches
Mail list logo
