Its included as part of the SAML 1.1 response, but not as part of the CAS
response.
Cheers,
Scott
On Tue, Oct 16, 2012 at 4:05 PM, Pronstad, Thomas wrote:
> Hi
>
> Does CAS support identifying which authentication handler was used by a
> user for authentication. Either via attributes or some
Greetings,
On Mon, Oct 15, 2012 at 5:24 PM, Jamie Johnson wrote:
> I have a service secured behind CAS which works properly but I'd like
> to remove the jsessionid from the URL, is this possible?
Why not just add to your web.xml:
true
true
-Jesse
--
There are 10 t
This fixed my problem thank you. I apparently got a little heavy handed when
copying files over for the maven overlay
-Original Message-
From: Marvin Addison [mailto:marvin.addi...@gmail.com]
Sent: Tuesday, October 16, 2012 12:35 PM
To: cas-user@lists.jasig.org
Subject: Re: [cas-user] CA
Hi
Does CAS support identifying which authentication handler was used by a user
for authentication. Either via attributes or some other way?
I'm looking for a way to support levels of authentication strength. The goal is
that an application during a service ticket validation can decide if it wi
Thanks Misagh. That worked. Looks like an opensaml dependency in
cas-server-core pom.xml was causing joda-time 1.6.2. Added an exclusion to it
and added a Joda-time 2.1 dependancy and everything works now.
Dependency in cas-server-core pom.xml
joda-time
Can you run the mvn dependency:tree (I think that is the command) to show
where it is coming from?
On Mon, Oct 15, 2012 at 8:34 PM, Jonathan wrote:
> I found why it is happening. jsp-2.1-6.1.14.jar is included in the
> cas/WEB-INF/lib. If I remove this jar, then it jsp compiles ok.
>
> How can
Yes, that seems to be it. I am not sure why it wasn't showing up in my
local maven repository manager (MRM) which proxies the OSS one.
Thanks for checking,
-Jesse
On Tue, Oct 16, 2012 at 11:08 AM, Scott Battaglia
wrote:
> Isn't it here?
> http://search.maven.org/remotecontent?filepath=org/jasig/
Awesome! Nice work. Would this be a candidate to go through incubation (I
would assume that incubation period would be short) to be an official
client?
On Mon, Oct 15, 2012 at 12:45 PM, Misagh Moayyed wrote:
> CAS Community,
>
> ** **
>
> It’s my pleasure to announce a fine new addition to
> nested exception is java.lang.IllegalArgumentException: Unknown entity:
> org.jasig.cas.ticket.registry.support.JpaLockingStrategy$Lock]
A common cause of this error is a custom persistence.xml as part of a
Maven WAR overlay that has not been updated with recent changes; in
this case addition o
What does MRM mean in this situation? Google returned some interesting
results :-)
On Mon, Oct 15, 2012 at 1:44 PM, Jesse Farinacci wrote:
> Greetings,
>
> It seems we started migrating to a oss.sonatype.org for our MRM
> solution. However this doesn't appear to have been performed
> correctly
Isn't it here?
http://search.maven.org/remotecontent?filepath=org/jasig/cas/client/cas-client-core/3.2.1/cas-client-core-3.2.1.pom
We use OSS to publish to the main repo, so they should be in sync.
On Mon, Oct 15, 2012 at 1:44 PM, Jesse Farinacci wrote:
> Greetings,
>
> It seems we started mig
>From the command line, execute: "mvn dependency:tree" and examine which
dependencies get resolved and exclude as needed.
-Misagh
> -Original Message-
> From: Abhijit Gaikwad [mailto:agaik...@fit.edu]
> Sent: Tuesday, October 16, 2012 6:28 AM
> To: cas-user@lists.jasig.org
> Subject: R
Looks like something is creating a dependency for joda-time-1.6.2.jar while
the cas-server-support-ldap is specifying joda-time 2.1. When I delete the
joda-time-1.6.2.jar from lib and restart tomcat it works fine. Haven't figured
out what is using the 1.6 yet as I couldn't find a dependency for
Try this link please:
https://github.com/Jasig/cas/tree/master/cas-server-integration-ehcache/src/test/resources
...and you may be able to use the following resources as starting points:
- ticketRegistry.xml
- ehcache-replicated.xml
-Misagh
> -Original Message-
> From: Andres [mailto:
I've attached an example ticketRegistry.xml that worked for us on CAS 3.5.1.
The ehCache configuration file is externalized to /etc/cas in this case (line
39).
Benjamin Mosior
-Original Message-
From: Andres [mailto:afolg...@gmail.com]
Sent: Tuesday, October 16, 2012 8:02 AM
To: cas-u
15 matches
Mail list logo
