Hi,
Does CAS support Facebook/twitter authentication? Or does it provides any hooks
for authenticating user against social networking websites along with Local
LDAP authentication? I am designing SSO solution for my company and one of the
requirement that business has come up with is that they
We had a good design discussion on the #jasig-cas channel today about
supporting this. I think Marvin is going to articulate one more JAAS use
case that we might want to fold into this and then we'll look at
implementing the solution.
Read through
https://wiki.jasig.org/display/CAS/jasig-cas+IRC+
I can't solve your logging problem. But assuming you do that, setting the
Java client to DEBUG *should* tell you what response came back from the CAS
server.
You could also try posting a sanitized web.xml (i.e. replace the real host
names if you're concerned) and we can see if there are any glari
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As of m-a-c 1.0.9, Proxy Validation is not implemented. Patches are
welcome! ;-)
On 02/28/2011 12:09 PM, Seyfi, Ismail wrote:
>
> Is this possible?
>
>
>
> I see the following:
>
>
>
> Directive: CASProxyValidateURL
> Default:https://login.uconn.edu
Hi all,
After speaking with colleagues at another nearby Uni, I decided to try their
approach to CASifying PeopleSoft.
The first step is to simply add CAS client filters to the Weblogic web.xml and
do the mappings. So far so good, when I hit my PeopleSoft applications I get
redirected to CAS a
> We are currently experiencing an issue with LDAP read timeouts not
> corresponding with settings set in CAS
> Our CAS generated
> LDAP search requests are always timing out at 2s as opposed to any other
> value inserted for the "com.sun.jndi.ldap.read.timeout" attribute in our
> deployerConfi
All,
We are currently experiencing an issue with LDAP read timeouts not
corresponding with settings set in CAS. After analyzing TCP dumps of
communication between our CAS & LDAP servers, it has been determined that
our CAS implementation is not functioning as expected. Our CAS generated
LDAP searc
Is this possible?
I see the following:
Directive: CASProxyValidateURL
Default:https://login.uconn.edu/cas/proxyValidate
Description: The URL to use when performing a proxy validation. This is
currently
an unimplemented feature, so setting this will have no effect.
In the documentation.
2011/2/24 Marvin Addison :
> My colleague noted this thread and shared the following link, which I
> believe describes how to do what you asked:
>
> http://download.oracle.com/javase/jndi/tutorial/ldap/misc/aliases.html
>
> You would specify this sort of JNDI configuration in the JNDI
> environment
