HipChat authentications are not updating the user's lastAuthenticated field in Crowd. Users must log into Crowd itself or another app, such as Jira, Confluence, etc., for the timestamp to be updated. This is a major problem for us as we have implemented a script that automatically deactivates users who have not logged in for 30 days. If a user only uses HipChat, and not any other app, their account will be deactivated as if they haven't logged in. Is this a known bug? Is there a solution or workaround?
HipChat does not write any information to external directories as it only performs the read function from them. As explained in the Crowd configuration page in HipChat Server:
Hence, the behavior that you are experiencing on your end is expected since HipChat do not have permission to modify any information to Crowd. It is built this way by design since HipChat only pulls information from Crowd, stores it in the database for authentication.
Whenever an external users logs in, authentication will be done against the data stored in the database instead of directly towards the external directory (Crowd, LDAP, etc.)
We hope that helps to clarify the situation. If you have any additional questions about this, please let us know.
...have mention name FirstnameLastname. Fe.: @MaartenCautreels This certainly helps to know who is being mentioned in a conversation. Imagine your colleague sends the following message...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot