You need to run over HTTPS to enable SSO.
Cheers,
Scott
On Thu, Mar 4, 2010 at 1:21 PM, boobe kaza wrote:
> Hi!
> I'm a newbie for central auth. service but today I succesfully install a
> CAS server on a glassfish2 and integrate it with two spring security web
> application. (praise to be
There's a tiny bit already at
http://www.ja-sig.org/wiki/display/CASUM/TicketRegistry+Cleaner
On Thu, Mar 4, 2010 at 4:42 PM, Marvin Addison wrote:
> > Can you point me to any documentation on the HA Registry Cleaner?
>
> It doesn't exist yet, but I'll be writing up some 3.4 documentation to
>
> Can you point me to any documentation on the HA Registry Cleaner?
It doesn't exist yet, but I'll be writing up some 3.4 documentation to
include that component at the Spring Jasig conference. I'll try to
remember to update this thread once it's completed.
M
--
You are currently subscribed t
Hi Scott,
Can you point me to any documentation on the HA Registry Cleaner?
Thanks,
Dean
--
View this message in context:
http://n4.nabble.com/CAS-3-4-Release-Candidate-1-tp1570893p1578684.html
Sent from the CAS Users mailing list archive at Nabble.com.
--
You are currently subscribed to
Hi Will,
From what you posted it looks like your SPNEGO configuration is
incomplete. I am successfully doing CAS + SPNEGO with my cas servers hosted
on RHEL v5.
Here is my list of credentialsToPrincipalResolvers in mydeployerConfig.xml
file
And here is my jcifs spnego auth ha
Hi All,
Finally pushing our implementation of CAS out to production and in an
attempt to clean up our cas.properties file I removed the following:
cas.securityContext.serviceProperties.service
cas.securityContext.casProcessingFilterEntryPoint.loginUrl
cas.securityContext.ticketValidator
Hi!
I'm a newbie for central auth. service but today I succesfully install a CAS
server on a glassfish2 and integrate it with two spring security web
application. (praise to be god!)
in spring sec app's configuration I set to false the serviceProperties
sendRenew attribute.
I thinked that is the s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am seeing lots of output -- just no errors when I get that to show on
the webpage.
Marvin Addison wrote:
>> log4j.logger.org.jasig.cas.adaptors.ldap.LdapPasswordWarningCheck=DEBUG
>> log4j.logger.org.jasig.cas.adaptors.ldap=DEBUG
>> log4j.logger.org
> log4j.logger.org.jasig.cas.adaptors.ldap.LdapPasswordWarningCheck=DEBUG
> log4j.logger.org.jasig.cas.adaptors.ldap=DEBUG
> log4j.logger.org.jasig.cas.ticket=DEBUG
> log4j.logger.org.jasig.cas=DEBUG
With those loggers you should see lots of output in the cas.log file
on authentication. If not, s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i already have this block in my logger:
log4j.logger.org.jasig.cas.adaptors.ldap.LdapPasswordWarningCheck=DEBUG
log4j.logger.org.jasig.cas.adaptors.ldap=DEBUG
log4j.logger.org.jasig.cas.ticket=DEBUG
log4j.logger.org.jasig.cas=DEBUG
I know it is red
Thank you for reply
but what I want to say is that If I access
http://www.casserver.com/logininstead of
www.foo.com or www.bar.com for the first time. the value of request
parameter service must be blank, or there is even no sush a request
parameter, right? and If I login in successfully, I will se
> Any suggestions on what logging to increase or where to start digging?
Turn the ldap logger to DEBUG in the log4j.properties file:
log4j.logger.org.jasig.cas.adaptors.ldap=DEBUG
If that doesn't provide anything helpful, put org.jasig.cas in DEBUG
and try again.
M
--
You are currently subscr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am trying to get BindLdap working so I can look the Ldap password
policy enforcement module, and am running into a snag.
I followed the documentation here to make the changes:
http://www.ja-sig.org/wiki/display/CASUM/LDAP
When I go to log in, I get
It said populate principal attributes in the title, so I thought maybe
that's all he needed. I guess we'll find out ;-)
On Thu, Mar 4, 2010 at 8:46 AM, Marvin Addison wrote:
> > You would only need a RDBMS resolver if you need to resolve the provided
> > username to something else stored in the
> You would only need a RDBMS resolver if you need to resolve the provided
> username to something else stored in the database.
That was my understanding of his use case, but maybe he could clarify
whether that is correct. I still think a JDBC resolver would be
generally useful.
M
--
You are c
You would only need a RDBMS resolver if you need to resolve the provided
username to something else stored in the database.
If you merely need attributes, then you just use one of the PersonDirectory
implementations with an existing resolver.
Cheers,
Scott
On Thu, Mar 4, 2010 at 8:35 AM, Marvin
> I tried but could not find RDBMS resolvers.
Neither could I. I imagined I would find a JDBC
CredentialsToPrincipalResolver in the cas-server-support-jdbc module,
http://developer.jasig.org/source/browse/jasigsvn/cas3/tags/cas-3-3-5-final/cas-server-support-jdbc/src/main/java/org/jasig/cas/adapt
There is no official pre-compiled version of mod_auth_cas for Windows,
but there are build instructions in README.win32. I think you will need
both: mod_auth_cas with Apache on Windows, and the x.509 handler at the
CAS server.
-Matt
-Original Message-
From: Richard Suematsu
Reply-to: "ca
Hi,
I tried but could not find RDBMS resolvers.
I would appreciate if you could provide me a link/location from where I can
refer to the RDBMS resolvers.
Thanks in advance,
Thanks & Regards,
Gokula
-Original Message-
From: Marvin Addison [mailto:marvin.addi...@gmail.com]
Sent: Tuesday
19 matches
Mail list logo
