- On the HipChat Server's MariaDB, we had case insensitive database collation. This allowed users to log into the application with any casing possible.
- It prevented casing-related variations in LDAP / Active Directory from creating two different users when using admin@EXAMPLE. com and firstname.lastname@example.org
- On PostgreSQL this is not the case. PostgreSQL by default does not have case insensitive collations, which means that all of the queries are now case sensitive. email@example.com and admin@EXAMPLE.COM are not the same.
- This is a regression from HipChat Server that can affect user authentication after a migration to HipChat Data Center
- HipChat Data Center 3.0.0
- HipChat Data Center 3.0.1
- Create a user with an email address firstname.lastname@example.org
- Once created, authenticate using admin@EXAMPLE.COM through the log in screen
The log in should be successful
The following ERROR will be logged under the /var/log/hipchat/atlassian-crowd.log:
Users will have to authenticate using the specific email address that is mapped to their account for now until the internal change to the database collation is made