Hello
The stack trace looks indeed the same. I'm using cas-client-core 3.4.0
but I will try a locally built 3.4.1-SNAPSHOT based on the current GIT
source. Thanks!
best regards,
-christian-
Am Wed, 12 Aug 2015 16:38:06 +0200
schrieb Jérôme LELEU lel...@gmail.com:
Hi,
Which CAS client
Ich bin bis zum 2. September 2015 nicht erreichbar. Ihre E-Mail wird nicht
gelesen und nicht weitergeleitet.
In dringenden Fällen wenden Sie sich bitte an das Geschäftszimmer:
off...@rz.tu-clausthal.de (Tel.: 05323/72-2045) oder an
supp...@rz.tu-clausthal.de
--
You are currently subscribed
Hello,
our department are evaluating CAS to implement in a government institution
that has openldap to authenticate.
When I try to authenticate get the error:
*WHO: [username: ext-clorrey]
WHAT: 'principal' cannot be null.
Check the correctness of @Audit annotation at the following audit point:
I could not find that utility, so I used a shell script that is *supposed* to
do the same thing:
#! /bin/sh
if [ ! -d $1 ]; then
echo Usage: $0 [FOLDER] 2
exit 1
fi
for file in $1/*.pem; do
ln -s $file `openssl x509 -hash
You'll need to look into your container/CAS logs to figure out why
authentication is failing.
-Original Message-
From: Karlos [mailto:kjlore...@gmail.com]
Sent: Thursday, August 13, 2015 5:34 AM
To: cas-user@lists.jasig.org
Subject: [cas-user] Cas 3.5.2.1 and ldap WHAT: 'principal'
Ich bin bis zum 2. September 2015 nicht erreichbar. Ihre E-Mail wird nicht
gelesen und nicht weitergeleitet.
In dringenden Fällen wenden Sie sich bitte an das Geschäftszimmer:
off...@rz.tu-clausthal.de (Tel.: 05323/72-2045) oder an
supp...@rz.tu-clausthal.de
--
You are currently subscribed
Can someone remove this person from the list? He seems to have
misconfigured a vacation message. Thanks.
Milt Epstein
Programmer in Computational Genomics
Institute for Genomic Biology (IGB)
University of Illinois at Urbana-Champaign (UIUC)
mepst...@illinois.edu
On Thu, 13 Aug 2015, Alexander
Hello Misagh Moayyed,
the cas/log only show
=
WHO: [username: ext-clorrey]
WHAT: 'principal' cannot be null.
Check the correctness of @Audit annotation at the following audit point:
execution(public abstract
Carl,
Thanks for the recommendation. I'll need to check with our program's
SSO/CAS expert to see if that might be a solution.
I still haven't had any success compiling mod_auth_cas under 10.10. Notes
at https://ucdavis.jira.com/wiki/display/IETP/mod_auth_cas+OS+X
provide a modified Makefile,
Check what attributes are being released from your LDAP server.
The items in the LDAP response may be provided as part of the authenticated
user info but not necessarily the released attributes.
Ray
From: Chris Irwin chris.ir...@sadasystems.com
Sent: August
I'm not sure what i'm missing here. I can see the attributes resolved but they
are never released to the client:
2015-08-13 16:31:20,456 DEBUG
[org.jasig.cas.authentication.LdapAuthenticationHandler] - Attempting LDAP
authentication for cirwin+password
2015-08-13 16:31:20,565 DEBUG
Using 4.0.0
I'm configuring single log out on some services and I have encountered a
situation I would appreciate some clarity on. For this particular use case, we
want the logout callback to be called if the user visits /cas/logout directly,
but not when the TGT expires and is cleared out by
Given the following scenario:
CAS URL: https://cas.example.com
Bogus unauthorized service URL: https://bogus.example.net
Real authorized serviceURL : https://authorized.example.org
User is tricked (by phish, perhaps) to visit
https://cas.example.com/cas/login?service=https://bogus.example.net
But wouldn't it be better to check against the registry first and
disallowing unauthorized service URLs before bothering with
authentication?
What CAS version are you on? That is the exact current behavior.
-Original Message-
From: Baron Fujimoto [mailto:ba...@hawaii.edu]
Sent:
14 matches
Mail list logo
