Project

General

Profile

Actions

Bug #7179

closed

incorrect password on KNB login causes tomcat error

Added by Matt Jones over 5 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
04/06/2017
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:

Description

If I (purposefully) give an incorrect error in logging in with my LDAP DN, I get a low-level tomcat error instead of an error that lets me try again.


Files

login-error.png (92.2 KB) login-error.png Matt Jones, 04/06/2017 03:39 PM
Actions #1

Updated by Lauren Walker over 5 years ago

  • Status changed from New to Resolved

This required some changes both in the d1_portal_servlet and MetacatUI.

I changed the portal servlet so that it handles errors better - e.g. when a username, organization, or password is missing OR when authentication fails. Now, when an error is caught, the portal servlet will redirect back to the given target with an 'error' URL parameter ('error=Unable%20to%20authenticate%20LDAP%20user') rather than throw a server error. So now the MetacatUI flow looks like this:

- User enters the wrong credentials and submits the login form
- LDAP auth fails in the d1 portal
- User is redirected back to the login form in MetacatUI with an error message

Actions

Also available in: Atom PDF