As our IDP  "Oracle IDSC" that we use for SAML authentication only provides email addresses in their assertion, we need the ability that authentication could also in parallel be performed via email and not only via the user name as this is also possible we many of our other applications (windows, sharepoint etc.). Or the SAML interface configuration must allow to configure the email address as mapping of the verified user instead of the current  unconfigurable fixed user name

Would love this feature in all Atlassian products not just Confluence.
Will be testing the plugin from Aviram

Can anyone please tell me what my username is for jira. Apparently it isn't that obvious.

Aviram, thanks for exploring this via a 3rd party solution. We are currently evaluating the add-on you mentioned but have encountered a few issues (e.g. with the add-on email does work as username but the original username no longer does). That's off topic for this post but I'm still mentioning it here as the related support page (http://www.support.wikistrat.com/) is currently returning a 404. For those of us interested in the add on how can we interact more with the developers?

Hi,

Im not sure if this helps you guys as a temp solution, but I've written a plugin that allows users to login using their emails instead of usernames.
This is for Confluence and Jira Server only.

https://marketplace.atlassian.com/plugins/com.wikistrat.confluence.email-login/server/overview
https://marketplace.atlassian.com/plugins/com.wikistrat.jira.email-login/server/overview

I hope this helps

This is something along with native SAML support that needs to be implemented to allow for multi organizational use. If we could allow more than one organization to use Confluence, we would move towards 5000+ licenses for our Atlassian products.

We run a collaboration site with 60+ organizations. As users may only participate sporadically, it is bad enough to need to remember a username as well as a password. We estimate that we will suffer a significant drop in adoption in our knowledge capture and collaboration site because people don't want to do a username lookup (via password reset) each and every time they use the system.

I even saw on the Atlassian Blog some months back an article on how "The username is dead". We couldn't agree more! A person's email is their unique identifier.

I would say regardless of the number of votes that you get on this Jira issue, you should implement this feature in the next release. (Perhaps people don't vote on it because they can't remember their Atlassian username??)

Believe me, people want it.