Details
-
Bug
-
Resolution: Fixed
-
Low
-
None
-
HCS 2.0.4
-
None
-
Severity 1 - Critical
Description
Summary
When using an evaluation license for HipChat Server v2.0.4, adding users from an external user directory fails. The following error is thrown in the /var/log/hipchat/atlassian-crowd.log file:
2016-09-19 21:00:14,638 hipchat-httpclient-callbacks:thread-219 ERROR [hipchat.sync.crowd.CrowdSyncManager] Failed to create user: HipChatUser{uid=null, external_id={hcs}test.user, email=test.user@exampleserver.com, name=Kerianne Menon, mention_name=null, title=null, timezone=null, is_deleted=false, group_admin=false, roles=[]}
2016-09-19 21:00:14,638 hipchat-httpclient-callbacks:thread-219 ERROR [hipchat.sync.crowd.CrowdSyncManager] Got HTTP error 400 (Bad Request), with body
{
"error": {
"code": 400,
"message": "Unable to create user. You must purchase more licenses in order to add additional users",
"type": "Bad Request"
}
}
Environment
- HipChat Server v2.0.4
- Connected to an external user directory
- Evaluation license in use
Steps to Reproduce
- Install HipChat Server
- Apply an evaluation license
- Upgrade to v2.0.4
- Integrate with an external user directory containing users that do not currently exist in HipChat Server
- Synchronize the directory
Expected Results
Users will be added to HipChat Server successfully.
Actual Results
The below exception is thrown in the altassian-crowd.log file:
2016-09-19 21:00:14,638 hipchat-httpclient-callbacks:thread-219 ERROR [hipchat.sync.crowd.CrowdSyncManager] Failed to create user: HipChatUser{uid=null, external_id={hcs}test.user, email=test.user@exampleserver.com, name=Kerianne Menon, mention_name=null, title=null, timezone=null, is_deleted=false, group_admin=false, roles=[]}
2016-09-19 21:00:14,638 hipchat-httpclient-callbacks:thread-219 ERROR [hipchat.sync.crowd.CrowdSyncManager] Got HTTP error 400 (Bad Request), with body
{
"error": {
"code": 400,
"message": "Unable to create user. You must purchase more licenses in order to add additional users",
"type": "Bad Request"
}
}
Workaround
No workarounds have been identified as this time.