In the meta model, it should be possible to disable ldap entirely. Right now when entering a wrong username/password, the following error message is displayed in the log:
2014/03/15 07:11:12.339 ERROR [ShiroLdapRealm] Could not connect to ldap://localhost:389/: javax.naming.CommunicationException: localhost:389 [Root exception is java.net.ConnectException: Connection refused]
2014/03/15 07:11:12.339 ERROR [ShiroLdapRealm] No LDAP server available.
2014/03/15 07:11:12.344 INFO [realm] Unable to authenticate with org.linkedin.glu.console.realms.ShiroLdapRealm - No LDAP server available.
2014/03/15 07:11:12.361 WARN [AuthFilters] Authorization failure: Authentication failed for token submission [org.apache.shiro.authc.UsernamePasswordToken - glua, rememberMe=false]. Possible unexpected error? (Typical or expected login exceptions should extend from AuthenticationException).
which should obviously not happen if not using ldap...
ypujante
commented
10 years ago
In the meta model, it should be possible to disable ldap entirely. Right now when entering a wrong username/password, the following error message is displayed in the log:
which should obviously not happen if not using ldap...