On Tue, Jul 22, 2014 at 8:58 AM, wrote:
> 2014-07-22T14:04:07.025312+02:00 ldap..unice.fr slapd[23702]: conn=1015 op=2
> SRCH attr=supannAliasLogin member mail displayName
> 2014-07-22T14:04:07.025312+02:00 ldap..unice.fr slapd[23702]: conn=1015 op=2
> SRCH base="uid=myuser,ou=personnel,ou=people
My bad i have found the ldap log.
When i used the replicat ldap i dont have the java error [LDAP: error code 32 -
No Such Object];
So its an other problem of filters.
But the problem authenticationResultCode=AUTHENTICATION_HANDLER_SUCCESS,
then
LdapAuthenticationHandler failed authenticating
is
hi,
I don’t understand...I see nothing in my ldap log (at log level 256). Nothing
like : "no bind", and "no connection" with my user...
I have tried with the bind admin ldap, and i have the same error and nothing in
the ldap log.
i am investigating…
--
On Mon, Jul 21, 2014 at 10:54 AM, wrote:
> Yes, thanks i see my attributes now.
> I confirm that my user can read the entry.
> The problem is the same..
What does your LDAP log say?
> [LDAP: error code 32 - No Such Object]; remaining name
> ‘uid=myuser,ou=personnel,ou=people,dc=unice,dc=fr']
T
Yes, thanks i see my attributes now.
I confirm that my user can read the entry.
The problem is the same..
-
Daniel CHARLOT
D.S.I. Université de Nice Sophia-Antipolis
Administrateur Systèmes et Réseaux
28, avenue de Valrose - BP 2135 -
On Mon, Jul 21, 2014 at 9:17 AM, wrote:
> In fact i dont know why my returnAttributes=[] are empty/null.
> Where configure that ?
Add
to your deployerConfigContext.xml
That should get the return attributes set correctly.
Confirm that the user has read access to their own entry.
--Daniel Fish
Hi,
I have found before :
2014-07-21 15:01:21,282 INFO [org.ldaptive.auth.Authenticator] - Authentication
succeeded for dn: uid=myuser,ou=personnel,ou=people,dc=unice,dc=fr
An error :
searchFilter=[org.ldaptive.SearchFilter@1642584434::filter=(objectClass=*),
parameters={}], returnAttributes=[],
Where to check this entry attribute.
>
> In the back end its giving Unable to validate proxy ticket validator issue.
>
> -Original Message-
> From: Vincent Repain [mailto:vincent.rep...@insa-rennes.fr]
> Sent: Friday, July 18, 2014 2:48 PM
> To: cas-user@lists.jasig.org
Where to check this entry attribute.
In the back end its giving Unable to validate proxy ticket validator issue.
-Original Message-
From: Vincent Repain [mailto:vincent.rep...@insa-rennes.fr]
Sent: Friday, July 18, 2014 2:48 PM
To: cas-user@lists.jasig.org
Subject: Re: [cas-user] CAS 4
Hi,
FWIW : I had a similar problem and the issue whas opendlap side (i
suppose that you are using openldap), where the bind was OK but the
search of the entry that followed returned no value.
Could you verify that self has read permission on "entry" attribute in
your tree (ou=personnel,ou=people
The root of the problem is that the authentication request doesn't
contain the principalIdAttribute, which you've defined as 'uid':
> request=[org.ldaptive.auth.AuthenticationRequest@1438545291::user=myuser,
> retAttrs=[]]
So the authenticated entry doesn't contain that attribute either:
> [org.ld
11 matches
Mail list logo