New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should be able to disable ldap in console #261

Closed
ypujante opened this Issue Mar 15, 2014 · 1 comment

Comments

Projects
None yet
1 participant
@ypujante
Member

ypujante commented Mar 15, 2014

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 ypujante added bug and removed bug labels Mar 15, 2014

@ypujante ypujante added pending and removed pending labels Aug 27, 2014

ypujante added a commit that referenced this issue Sep 8, 2014

@ypujante

This comment has been minimized.

Member

ypujante commented Sep 11, 2014

Implemented in 5.5.2

@ypujante ypujante closed this Sep 11, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment