Known issues and limitations of external directory synchronization

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Fisheye および Crucible は除く

目的

This article lists a number of known issues and limitations that could prevent Hipchat Server admins from observing a desired behaviour after syncing an external directory. 

For the sake of simplicity, we will refer to any type of user directory such as LDAP, Crowd, AD, etc... as the directory. 

On this page:

The sync is reported as successful but user attributes are not updated

説明

User attributes are changed in the directory and the admin hits the Synchronize button. User attributes such as Full name or Email are not updated. 

Cause and Resolution

1. The user is local to Hipchat and not linked to a user in the directory

Go to Group admin > Users and click on the user in question. If you're able to edit the Full name and the Email fields then the user is local to Hipchat. Had the user been an external user, these fields should be greyed out as shown in the screenshot below: 

If the user was external and became local after deactivating/re-activating, you hit  HCPUB-820 - Getting issue details... STATUS . In order to work around the issue, run a full sync via Group admin > Authentication > External directory > Configure > Directory > Disable then Enable and the user will become external. 

2. The update in the directory was made to the user id

If one of the updated fields in the directory is the attribute mapped to User Name Attribute in Group admin > Authentication > External directory > Configure > Edit > User Schema Settings, an incremental sync will fail and throw the following exception to /var/log/hipchat/atlassian-crowd.log

java.lang.RuntimeException: com.atlassian.crowd.event.EventTokenExpiredException: com.atlassian.crowd.event.user.UserRenamedEvent is not supported by incremental sync. 

This is the behaviour by design. The user id attribute can be updated by running a full sync via Group admin > Authentication > External directory > Configure > Directory > Disable then Enable. Before running this, be sure to check A new user is created instead of updating an existing user.

注意

  • Disable/Enable does not disconnect online users. 

  • Disable/enable runs a full sync. This can also be triggered by stopping/starting Crowd via the command line.

    sudo dont-blame-hipchat -c '/etc/init.d/crowd stop && /etc/init.d/crowd start' 

A new user is created instead of updating an existing user

説明

The existing users attributes are not updated. Instead, a new user is created in Hipchat. The new user has the new attributes but has no chat history. 

Cause and Resolution

Users in Hipchat are mapped to users in the directory by user id, which is the attribute mapped to User Name Attribute in Group admin > Authentication > External directory > Configure > Edit > User Schema Settings. If no match is found using the id, the sync process will search using the email. If no match is found, a new user will be created. This is the behaviour by design.  

Therefore, updating the user id and the email at the same time will result in creating a new user in Hipchat. If you would like to update both the user id and the email, make one update at a time, sync, then make another update as follows: 

  1. Update user id in the directory
  2. Group admin > Authentication > External directory > Configure > Directory > Disable then Enable
  3. Update email in the directory 
  4. Group admin > Authentication > External directory > Configure > Synchronize

注意

  • Disable/Enable does not disconnect online users. 

  • Disable/enable runs a full sync. This can also be triggered by stopping/starting Crowd via the command line.

    sudo dont-blame-hipchat -c '/etc/init.d/crowd stop && /etc/init.d/crowd start' 


This limitation will be addressed once  HCPUB-1137 - Getting issue details... STATUS  is implemented. 

If a new user was created already, contact Hipchat Server Support for the steps to fix the issue.

A user name is not updated

説明

A user name longer than 50 characters in the directory will not be reflected in Hipchat. 

Cause and Resolution

HCPUB-1763 - Getting issue details... STATUS  is a feature request to increase the limit beyond 50 characters. Until it's implemented, user name have to be shorter than 50 characters in the directory, otherwise, they will not be synced. 

回避策

AD attributes may be concatenated within Hipchat to make the display name shorter. For instance, you can combine the first and last name by entering givenName + " " + sn in the User Display Name Attribute field.


最終更新日 2018 年 11 月 2 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.