Hi Scott,
Agenda item:
Getting .Net supported and documented at JASIG.
Do you want me to prepare and send you and Marvin an Elluminate session for
this one?
Kim
On May 4, 2010, at 7:07 AM, Scott Battaglia wrote:
> All,
>
> The next community call will be May 12 @ 12pm Eastern. We've got ou
In the latest version of CAS, we're using Spring Web Flow 2, so you'll need
something like this:
Cheers,
Scott
On Wed, May 5, 2010 at 2:18 PM, aruhi wrote:
> I am working with cas-server-3.4.2 and following the steps given for
> Configurati
Its about as scoped down as you can get (specifically to the CAS domain, no
sub-domains, secure only, and the /cas path)
On Wed, May 5, 2010 at 12:54 PM, Curtis Garman wrote:
> Scott, can you give me a little more insight into what the default behavior
> is doing or allows? Does the default beha
Your previous problem and the errors below suggest you're missing
arbitrary files:
> log4j:WARN No appenders could be found for logger
> (org.springframework.web.context.ContextLoader).
> log4j:WARN Please initialize the log4j system properly.
Above is caused by missing /WEB-INF/classes/log4j.pro
One issue I can see is that instead of entering SSO credentials into the
CAS web ui, you are now entering SSO credentials into the "web service
client". Scott's oft repeated view (I think) is that only entering creds
into one server side application is an indispensible security advantage.
Personall
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We handle deployment to our servers as follows:
We have 8 servers total 2 dev (cas dev use only), 2 test (developer
dev/test), 2 stage (development stage), 2 prod (self explainitory). I
set an environment variable (TIER) on each tier appropriately, an
Our institution's ¢2:
We currently use the Maven 2 overlay, but have opted to modify the pom.xml and
add a few properties files to allow for multiple environments. This is done via
enabling a particular build profile that would filter multiple environment
specific variables accordingly.
We als
> I did notice that when I did the mvn clean package, that I had to create the
> file ~/src/main/webapp/WEB-INF/web.xml for it to build successfully.
The source tree contains a valid web.xml at that path, so I'm puzzled
why yours was apparently missing. You certainly need a web.xml
deployment de
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
STOP READING MY SOURCE CODE.
Ok, it's open source, so carry on -- in fact, I would like to share.
I did not like using localhost for the services console, so I made the
following changes:
cas.securityContext.serviceProperties.service=${protocol.htt
> Next I changed the pom.xml and deployerConfigContext.xml IAW. with
> directions in:
> http://www.ja-sig.org/wiki/display/CASUM/Best+Practice+-+Setting+Up+CAS+Locally+using+the+Maven2+WAR+Overlay+Method
> , and after copying the new cas.war file to the webapps folder and
> restarting tomcat,
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
Have you tried the localhost error log?
On Wed, May 5, 2010 at 1:43 PM, rob mckennon wrote:
> good afternoon list.
>
> I have installed CAS-3.3.5 on CentOS linux and made it through the first
> "mvn clean package", copied the ~target/cas.war file to the tomcat/webapps
> folder, restarted tomca
good afternoon list.
I have installed CAS-3.3.5 on CentOS linux and made it through the first
"mvn clean package", copied the ~target/cas.war file to the tomcat/webapps
folder, restarted tomcat and it worked! (i.e. login with userID=passwd)
Next I changed the pom.xml and deployerConfigCo
On Wed, May 5, 2010 at 1:01 PM, Marvin Addison wrote:
> >> No. The host.name property is used in at least a couple of places and
> >> should be the valid FQDN of the server.
> >
> > It shouldn't be. We always named ours cas1 and cas2 :-)
>
> You're right. I grepped through the source and the on
Ah...ok I got ya...yeah I don't like creating extra files just to have extra
files unless there is a purpose...creating another file inside the war
doesn't make sense to me but reading the value in from something outside the
app does.
On Wed, May 5, 2010 at 12:02 PM, Scott Battaglia
wrote:
> If y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'll second this.
Marvin Addison wrote:
>> The benefit of the method described in the Clustering docs is that you pull
>> the configuration out of the war file, and make it host specific, and you
>> can roll the same war file to all servers in the cl
If you're using Maven2 WAR Overlay and you want to modify the value, you
would need to place a copy of the file in your overlay and edit that (which
is what I meant by new version).
Alternatives include changing the id generators to read that value from
somewhere else (as someone pointed out). At
>> No. The host.name property is used in at least a couple of places and
>> should be the valid FQDN of the server.
>
> It shouldn't be. We always named ours cas1 and cas2 :-)
You're right. I grepped through the source and the only configuration
references deal with ticket ID:
cas-server-webap
Scott, can you give me a little more insight into what the default behavior
is doing or allows? Does the default behavior use maximum protection?
On Wed, May 5, 2010 at 10:53 AM, Scott Battaglia
wrote:
> You don't need to set or change it. The value, as is, is fine.
>
>
> On Wed, May 5, 2010 at
> The benefit of the method described in the Clustering docs is that you pull
> the configuration out of the war file, and make it host specific, and you
> can roll the same war file to all servers in the cluster.
+1 for this approach. We are _very_ happy using a single deployable
across 6 server
Marvin, I'm referring to the wiki page you referenced at
http://www.ja-sig.org/wiki/display/CASUM/Clustering+CAS and the section
"Guaranteeing Ticket Uniqueness" ...it seems like I should be able to
include the cas.properties in my maven overlay and update the value here
instead of creating a new f
Scott, shouldn't this file be part of my maven overlay anyway since it is
here that I would need to configure the services stuff?
On Wed, May 5, 2010 at 10:44 AM, Scott Battaglia
wrote:
> On Wed, May 5, 2010 at 11:36 AM, Curtis Garman wrote:
>
>> Marvin, do you mean the host.name in the cas.prope
On Wed, May 5, 2010 at 11:45 AM, Marvin Addison wrote:
>
>
> No. The host.name property is used in at least a couple of places and
> should be the valid FQDN of the server.
>
It shouldn't be. We always named ours cas1 and cas2 :-)
>
> M
>
> --
> You are currently subscribed to cas-user@list
On Wed, May 5, 2010 at 11:36 AM, Curtis Garman wrote:
> Marvin, do you mean the host.name in the cas.properties file? It looked
> like the documentation wanted you to create a whole new properties file and
> such (even for cas 3.3.5). Isn't it as easy as editing the default value of
> the host.nam
The benefit of the method described in the Clustering docs is that you
pull the configuration out of the war file, and make it host specific,
and you can roll the same war file to all servers in the cluster.
If in cas.properties, you need custom war files per server. (The var
name doesn't matter
You don't need to set or change it. The value, as is, is fine.
On Wed, May 5, 2010 at 11:44 AM, Curtis Garman wrote:
> Reading through the
> http://www.ja-sig.org/wiki/display/CASUM/Clustering+CAS wiki page, I had a
> question about cookie visibility and the cookieDomain bean property. I'm
> cu
> do you mean the host.name in the cas.properties file?
Yes. I was citing from memory, which is clearly hazy.
> It looked like
> the documentation wanted you to create a whole new properties file and such
> (even for cas 3.3.5).
What documentation are you referring to?
> Isn't it as easy as ed
Reading through the
http://www.ja-sig.org/wiki/display/CASUM/Clustering+CASwiki page, I
had a question about cookie visibility and the cookieDomain
bean property. I'm curious why the default configuration files don't define
any cookieDomain at all? The value listed on the wiki is
p:cookieDomain="e
Marvin, do you mean the host.name in the cas.properties file? It looked like
the documentation wanted you to create a whole new properties file and such
(even for cas 3.3.5). Isn't it as easy as editing the default value of the
host.name property already defined? Also, am I correct in assuming that
I'm probably looking at all the open issues targeted towards the next
release this weekend.
Cheers,
Scott
On Wed, May 5, 2010 at 11:11 AM, Marvin Addison wrote:
> Anyone had time to look at the patch for
> http://www.ja-sig.org/issues/browse/CASC-108? I'm itching to get it
> included in the ca
Anyone had time to look at the patch for
http://www.ja-sig.org/issues/browse/CASC-108? I'm itching to get it
included in the cas-client release. Our testing has shown it works
well in JBoss 5.1. If no one has any concerns, I'm happy to commit
it.
M
--
You are currently subscribed to cas-user@
Based on what I've learned so far, it seems like using the RESTful API for web
service authentication is a reasonable option. Since the target web services
are part of our application, there is no need for proxying. Information about
the RESTful API can be found at
http://www.ja-sig.org/wiki/
Jose,
Thank you very much for your replies. They were very helpful and I really
appreciated them!
Pat
-Original Message-
From: José Miguel Parrella Romero [mailto:joseparre...@gmail.com]
Sent: Tuesday, May 04, 2010 6:00 PM
To: cas-user@lists.jasig.org
Subject: Re: [cas-user] differen
Which version of CAS are you using?
On Wed, May 5, 2010 at 5:35 AM, Lars Preben Sorsdahl wrote:
> I tried to enable JPA ticket registry (PostgreSQL database), but I'm
> experiencing some problems with CAS. When I add the hibernate-entitymanager
> dependency, according to the CAS documentation, t
I tried to enable JPA ticket registry (PostgreSQL database), but I'm
experiencing some problems with CAS. When I add the hibernate-entitymanager
dependency, according to the CAS documentation, to my custom overlay pom.xml,
authentication fails. It's quite strange since I haven't changed the tick
37 matches
Mail list logo
