Product: TIBCO Spotfire®
Duplicate user accounts with different domain names are seen in "Users & Groups" view of the Administration console after LDAP is synchronized.
There are scenarios where users from different domain names get synchronized displaying duplicate accounts with two different domains, one with user@domain.com and the other with SPOTFIRE(see below screenshot).
The most common reason could be if you change the collapse domain setting AFTER a LDAP sync has already been performed. If so, it is not recommended to change the collapse domains configuration property after once having synchronized Spotfire Server with an external directory. Doing so will lead to double accounts with different domain names for every synchronized user and group in the User Directory. The new accounts will not inherit the permissions of the old accounts.
Note: If the users are logged in with default "SPOTFIRE" domain successfully but lost the permissions then you will need to grant required permissions to access the Spotfire Analyst/Webplayer or access any analysis files. However, this is not required if you want to use LDAP Active Directory.
One of the following solution might apply here:
- If the user's are disabled already in Spotfire database then following KBA "How to remove disabled synchronized users from TIBCO Spotfire" will resolve the issue.
- If the user's are enabled then we will have to manually update them as disabled in the Spotfire database and then following the KBA " How to remove disabled synchronized users from TIBCO Spotfire ". Below are the steps to manually disable users:
- Take the Full backup of Spotfire Database
- Update the enabled flag to 0 for user's with domain that you would want to remove. For example
Update USERS set [ENABLED]=0 where domain_name = 'na.tibco.com'
- Once the user's are disabled you can run the command delete-disabled-users following KBA "How to remove disabled synchronized users from TIBCO Spotfire"
KBA: How to remove disabled synchronized users from TIBCO Spotfire. Doc: delete-disabled-users
Comments
0 comments
Article is closed for comments.