Skip to content
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

Active Directory login summary shows 'Email address: null' #5043

Closed
matt-richardson opened this issue Oct 31, 2018 · 2 comments

Comments

@matt-richardson
Copy link
Contributor

commented Oct 31, 2018

Prerequisites

  • I have verified the problem exists in the latest version
  • I have searched open and closed issues to make sure it isn't already reported
  • I have written a descriptive issue title
  • I have linked the original source of this report
  • I have tagged the issue appropriately (area/*, kind/bug, tag/regression?)

The bug

The summary (header) description for the Active Directory identity is showing Email address: null.

What I expected to happen

The summary description to not include null. It should show the first available claim that is not null.

Steps to reproduce

  1. Enable active directory authentication
  2. Create a new user
  3. Add an active directory identity
  4. Collapse the active directory section
  5. note the summary says Email address: null

Screen capture

collapsed:
image

expanded:
image

Affected versions

Octopus Server: 2018.3.5 onwards

Workarounds

Expand the section to see the details.

Links

source: internally reported

@octoreleasebot

This comment has been minimized.

Copy link

commented Nov 1, 2018

Release Note: Show more informative summary text for an Active Directory identity when the specified account has no email address set

@lock

This comment has been minimized.

Copy link

commented Jan 30, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
2 participants
You can’t perform that action at this time.