[MGNLLDAP-47] Improve output of tester tool Created: 16/Dec/10  Updated: 27/Jul/11  Resolved: 09/Jun/11

Status: Closed
Project: LDAP Connector
Component/s: None
Affects Version/s: None
Fix Version/s: 1.4.3

Type: Improvement Priority: Neutral
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   
> User: null

I'd have to double check (i.e edit this issue before starting to work on it), but this "null" can be ignored. Of course, printed as such, it seems like an error to users of the tester tool. If the "null" can be ignored, either the line should't be printed all, or it should have a comment such as "User: null (can be ignored)"

> Group names: 
> Role names: 

This simply means that no group and role was resolved for the given user. It could be more explicit:

> Group names: (none)
> Role names: (none)

The tool could also hint the user to look at the log files if they need more details.



 Comments   
Comment by Zdenek Skodik [ 16/Dec/10 ]

this "null" can be ignored

it's printed although the user is successfully authenticated:

> Trying to log in as uid=user2,ou=People,dc=example,dc=com with a password.
> Login result: true
> Commit result: true
> Subject: Subject:
Principal: EntityImpl[name=user2]

> User: null

Generated at Mon Feb 12 02:21:03 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.