Coeurcy,
What do cas logs say about the ldap search (on debug or trace)?
Is sAMAccountName the/an attribute in the search tree? You are using cn in the
bind.
Ray
On Fri, 2023-05-26 at 12:07 -0700, Coeurcy Mokoko wrote:
Notice: This message was sent from outside the University of Victoria email
NB: I have now been able to raise the notification mentioned in my first
email above but I am unable to connect to CAS Server with: username: admin
; password: @Debian453, configured in cas.properties, which is my ldap user.
Le vendredi 26 mai 2023 à 19:53:15 UTC+1, Coeurcy Mokoko a écrit :
>
Ray,
In relation to what you said I've made some modifications to
"cas.properties" above but still "username/password" incorrect, as far as
ldap is concerned I can't find or access the logs for it, and it's case
sensitive.
My new cas.properties:
as.server.name=http://acsi.cg:8443
cas.server.
Coeurcy,
The ldap loggers from my previous email should help with debugging the problem.
Do you have access to the ldap server logs?
Is your ldap case sensitive (you have 'dc' and 'DC')?
Is there a class identifier missing in bind-dn?
Ray
On Fri, 2023-05-26 at 02:22 -0700, Coeurcy Mokoko wrote
Yes, I manage to connect from the command line with the same parameters,
but when I try to authenticate to cas with the same login and password, it
doesn't work!
Le mardi 23 mai 2023 à 18:08:03 UTC+1, Ray Bon a écrit :
> azer,
>
> Can you connect to your ldap server from the computer running ca
