Environment:
OpenLDAP 2.4.22
JASIG CAS 3.3.5
cas-server-support-ldap-pwd-expiration-3.3.5
I have been trying get the LDAP Password Policy module to work for several days
without success.
I have tested the OpenLDAP server with the command line client to ensure that
the proper error codes return
Hey, acevedo,
Thanks a lot! That works pretty good! --Jerry
>>> acevedo 7/30/2010 2:38 PM >>>
As I understand it ³request.getSession().invalidate()² still leaves
you
signed into CAS. So when you reload your application it will just
reauthenticate. You need to invalidate the session and direc
As I understand it ³request.getSession().invalidate()² still leaves you
signed into CAS. So when you reload your application it will just
reauthenticate. You need to invalidate the session and direct the user to
the cas servers logout page.
Http(s):// wrote:
> I have some issues with single si
I have some issues with single sign on/out. In CAS service, I add all my client
apps to database, with SSO participant set as "True", and in client
application's DD, I set "renew=false". In this case, seems single sign on works
pretty well: after I signed in from client app1, I can access client
I get the error when i deploy the war file using Tomcat 5.5, the errors are
located in catalina.out. I have no problems deploying 3.3.5 using the same
method.
Any ideas?
Thanks
Steve
cas-user@lists.jasig.org on Thursday, July 29, 2010 at 11:17 PM -0500 wrote:
>Both releases are security release
What should I be looking at and in what file? What am I missing? World
peace can it ever be achieved?
History
OK I have a CAS client and and CAS server setup running on a single server
in the same server instance of Glassfish. Everything seems to be working.
I can use themes and get attribute
Thanks a lot Scott! You give me a lot of help on understanding CAS. For now I
have set up a very default cas, and several applications are using it as
authentication server. The first step seems pretty good!
I think I am still not quite clear about proxy ticket, so in all my client app,
I just
Greetings,
I thought I had this working but apparently I was working against an
unsecured instance! Yikes.
My normal day to day operations are working great. Users are
authenticated against our LDAP instance and most everyone is happy.
When I try to access a REST service programmatically I am sta
The issue ended being the "filterProcessUrl", I recently switched from using
jetty to tomcat and forgot to account for the context path.
However, since correcting this issue, when I provide credentials to the CAS
login page and the CAS server acknowleges authentication (in its log), I'm
alway
Thanks for the reply Scott,
To request for another ticket, wouldn’t that require the user to
re-authenticate? I know there is a renew option but this forces the user to
re-authenticate which I would like to avoid. The idea is for the user to have
control of extending the CAS session while alr
Take a look at this link:
https://wiki.jasig.org/display/CASUM/Best+Practice+-+Setting+Up+CAS+Locally+using+the+Maven2+WAR+Overlay+Method
Cheers,
Scott
On Fri, Jul 30, 2010 at 7:40 AM, wrote:
> The deployerConfigContext has not been deprecated. Where did you read that?
>
> Merely copying the LD
The deployerConfigContext has not been deprecated. Where did you read that?
Merely copying the LDAP support is not sufficient. You need its dependencies
too. That's better managed using the Maven WAR Overlay process. We have it
documented in our wiki. I'll see if I can get you the link when I ge
Hello,
I was using the pre-built webapp war, which had the Spring LDAP support
in 3.3.5, which is now obviously failing in 3.4.2.
The documentation says that it must used as of 3.1, presumably as
opposed to cas-server-support-ldap. I don't see any pre-built Spring
LDAP jars anywhere in the
13 matches
Mail list logo
