You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Possibly too late for the original poster, but maybe this will help someone
else. Here is commentary of the log entries as I understand them:
2013-10-18 15:22:40,018 DEBUG [http-bio-8080-exec-10]: ldap
filter=(&(objectclass=person)(uid=emsa\web_user))
--- The ldap will be searched for an object where objectclass=person and the
uid=emsa\web_user
--- The fact that you are searching on the uid attribute suggests your ldap
server is something other than microsoft active directory, since uid is not
used by default on that directory platform
2013-10-18 15:22:44,596 INFO [http-bio-8080-exec-10]: No results found for
search, base: 'dc=emsa,dc=local'; filter:
'(&(objectclass=person)(uid=emsa\web_user))'.
--- Searching the ldap directory with a base of dc=emsa,dc=local, for a user
where uid=emsa\web_user failed. Possibly the uid syntax you are using is wrong
for your directory; no user could be found where uid=emsa\web_user. It is also
possible that the user you configured in webpasswordsafe-service.xml (property
name="userDn"...) does not her permission to read the uid attribute of the user
that has emsa\web_user set.
2013-10-18 15:22:44,596 DEBUG [http-bio-8080-exec-10]: LdapAuthenticator: login
success for emsa\web_user? false
--- Ldap authenticator concluded the login was unsuccessful
2013-10-18 15:22:44,596 DEBUG [http-bio-8080-exec-10]: CompositeAuthenticator:
login success for emsa\web_user? false
--- Composite authenticator concluded the login was unsuccessful
2013-10-18 15:22:44,597 DEBUG [http-bio-8080-exec-10]:
net.webpasswordsafe.common.model.User{id=6, username=emsa\web_user,
lastLogin=null, [email protected], activeFlag=true,
authnPassword=<uninitialized>, dateCreated=2013-10-18 15:22:20.0, type=U,
groups=<uninitialized>, fullname=Web Password User}
--- A user was found in the webpasswordsafe user database with username
matching emsa\web_user, but was not logged in due to failing the authentication
stage
If you are using openldap or similar, a possible next step would be to query
the actual uid value of the account you are attempting to log in with. The page:
https://www.centos.org/docs/5/html/CDS/ag/8.0/Finding_Directory_Entries-Using_ld
apsearch.html
might help to get you started with that if you are not familiar with the process
If you happen to be using microsoft active directory, there are a couple of
changes to consider:
1) in webpasswordsafe-service.xml, change the filter to:
<property name="filter" value="(&(objectclass=person)(sAMAccountName=$1))" />
2) configure your users in webpasswordsafe to use only the sAMAccountName - in
this case "web_user"
Original issue reported on code.google.com by
[email protected]
on 18 Oct 2013 at 2:58The text was updated successfully, but these errors were encountered: