From: Scott Battaglia [mailto:scott.battag...@gmail.com]
Sent: Tuesday, June 01, 2010 3:03 PM
To: cas-user@lists.jasig.org
Subject: Re: [cas-user] mail attribute
Did you choose the attribute in the multi-select field for the service?
On Tue, Jun 1, 2010 at 10:37 AM, McKennon, Robert
wrote:
Is a samlValidate only good for a one-time check?
I was using SOAP-UI to check for returned attributes and noticed that if
I re-post the same samlValidate message, it comes back "ticket # not
recognized".
Rob.
Unix Admin (fish out of water)
--
You are currently subscribed to cas-user@lis
I think I'm getting closer...
I have 3 entries in the "Services Management":
Services Management
http://localhost:8080/cas/services/*
SharePoint
http*://192.168.169.72:11123/*
Test
http*://192.168.167.74*
If I put this url (
https://fl028centos:8443/cas/login?service=http://192.168.16
g for this keyboard
:-)
Sent from my Verizon Wireless BlackBerry
____
From: "McKennon, Robert"
Date: Mon, 31 May 2010 18:27:33 -0400
To:
Subject: RE: [cas-user] mail attribute question
Scott,
So, the first thing to do in the management t
the attribute to the service via the service management
tool? Attribute release is controlled.
Sent from my Verizon Wireless BlackBerry
____
From: "McKennon, Robert"
Date: Mon, 31 May 2010 17:34:38 -0400
To:
Subject: [cas-user] mail attribute question
I'm looking to retrieve an attribute from LDAP (specifically "mail")
upon a samlValidate. But testing with SoapUI, I only see the
NameIdentifier being returned. Can someone tell me what I am missing?
I've seen other posts online where their "POST" is exactly like this,
but they get a lot more re
-Original Message-
From: Marvin Addison [mailto:marvin.addi...@gmail.com]
Sent: Tuesday, May 25, 2010 11:03 AM
To: cas-user@lists.jasig.org
Subject: Re: [cas-user] cas tickets x.509
> When CAS grant a ticket after a successful login, is the ticket signed
with
> a server x.509 cert?
The
I'm not sure how to ask this question, so here it goes anyway
When CAS grant a ticket after a successful login, is the ticket signed
with a server x.509 cert?
If so, does it use the default tomcat cert used for SSL, or did I miss
something in the configuration?
Does it encrypt the ti
-Original Message-
From: Marvin Addison [mailto:marvin.addi...@gmail.com]
Sent: Thursday, May 13, 2010 2:38 PM
To: cas-user@lists.jasig.org
Subject: Re: [cas-user] SAML token
> So I tried using:
>
> wget --output-document=out.txt --post-file=post.txt
> "http://192.168.168.83:8080/cas/s
Good Afternoon,
After too many hours of head-banging, I finally got CAS working against
my LDAP server. (for those who know what they are doing, it's probably
a straight-forward process).
All I have to do now is verify that SAML is granting tokens, and my part
in this project DONE!
Howeve
Does this error message mean that I'm getting close?
Could this be an authentication error finally contacting the LDAP
server?
2010-05-12 11:38:42,755 INFO
[org.jasig.cas.services.DefaultServicesManagerImpl] -
2010-05-12 11:38:42,895 ERROR
[org.springframework.web.context.ContextLoader] -
Darnit... I read that post and made a mental note to myself to change
it!!! (But of course, I got distracted by something stupid and didn't
do it right away).
Anyhow after that change:
2010-05-11 18:26:56,985 ERROR
[org.springframework.web.context.ContextLoader] -
org.springframework.beans.
Perhaps I'm getting closer... maybe.
2010-05-11 17:11:05,317 INFO
[org.jasig.cas.services.DefaultServicesManagerImpl] -
2010-05-11 17:11:05,417 ERROR [org.springframework.web.context.ContextLoader] -
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'centr
Thank you Marvin.
I did read that thread hoping I could find something in there that would
help me out.
But I think it's so far over my head that I can't make heads or tails of
it.
I changed the service line from Jpa to InMemory as listed below, but now
I get:
2010-05-11 16:35:10,570 ERROR
[or
Bernard, while I am NO expert on CAS, and I haven't even got it working on
LDAP yet, I do know that you need to add the dbcp dependency to your pom.xlm:
commons-dbcp
commons-dbcp
1.2.2
While I'm getting closer to getting this setup, I have ran across this
error. Am I missing a jar file or something obvious?
I received this error when trying to start the CAS server from the
tomcat manager.
2010-05-07 15:05:41,240 ERROR
[org.springframework.web.context.ContextLoader] -
glia [mailto:scott.battag...@gmail.com]
Sent: Thursday, May 06, 2010 9:13 AM
To: cas-user@lists.jasig.org
Subject: Re: [cas-user] problem at step 2
You're missing the CAS war file. That part isn't optional :-)
On Thu, May 6, 2010 at 9:09 AM, McKennon, Robert
wrote:
Sure!
[
@lists.jasig.org
Subject: Re: [cas-user] problem at step 2
Can you post your pom file? (expunging any proprietary info ;-))
On Thu, May 6, 2010 at 8:53 AM, McKennon, Robert
wrote:
-Original Message-
From: Marvin Addison [mailto:marvin.addi...@gmail.com]
Sent: Wednesday, May 0
-Original Message-
From: Marvin Addison [mailto:marvin.addi...@gmail.com]
Sent: Wednesday, May 05, 2010 6:19 PM
To: cas-user@lists.jasig.org
Subject: Re: [cas-user] problem at step 2
Your previous problem and the errors below suggest you're missing
arbitrary files:
> log4j:WARN No appe
So, I copied the web.xml file from the source tarball
(/usr/local/src/cas-server-3.3.5/cas-server-webapp/src/main/webapp/WEB-I
NF/web.xml) to my $PROJ_HOME/src/main/webapp/WEB-INF/ directory.
Rebuilt the package from my $PROJ_HOME (mvn clean package)
Things looked good.
I shutdown tomcat,
remov
-Original Message-
From: Marvin Addison [mailto:marvin.addi...@gmail.com]
Sent: Wednesday, May 05, 2010 2:36 PM
To: cas-user@lists.jasig.org
Subject: Re: [cas-user] problem at step 2
> Next I changed the pom.xml and deployerConfigContext.xml IAW. with
> directions in:
> http://www.j
Just checked that one too, nothing useful. Just the fact that the
services shutdown and started back up.
[r...@fl028centos logs]# tail -15 localhost.2010-05-05.log
INFO: ContextListener: contextDestroyed()
May 5, 2010 12:41:19 PM org.apache.catalina.core.ApplicationContext log
INFO: Closing
22 matches
Mail list logo
