HipChat not updating Crowd lastAuthenticated

Jesse Wisener November 14, 2017

Environment information:

  • HipChat 2.2.4 (2017.04.24.053859)
  • Crowd Version: 2.10.1 (Build:#685 - 2016-09-13)
  • All directories originate in Crowd; no integrations with LDAP, AD, etc.
  • HipChat has full permissions to update Crowd.

Problem:

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?

1 answer

1 accepted

0 votes
Answer accepted
AhmadDanial
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 15, 2017

Hi, Jesse.

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:

Screen Shot 2017-11-16 at 13.15.57.png

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.

Jesse Wisener November 16, 2017

This is very disappointing. Thank you for your answer.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events