8/21/2023 0 Comments Jira client reports read onlyImportant: I f users in Crowd are coming from Active Directory backed sources configured in "connector" mode (as opposed to Delegated), the LDAP user configured in Crowd must have ability to write back to LDAP. This is not recommended unless you really know what you are doing and what the impact on other applications using those directories may be. The following example applies to Atlassian Crowd.īe cautious when modifying other types of user directories such as Active Directory backed directories. ![]() The settings that need to be changed vary depending on the external directory software you are using. Step 2 - Update directory permissions externallyĮven if the Atlassian host application is set to Read/Write, it is still possible for the permissions on the external directory to block modifications coming from Confluence or Jira Software. Example with an Atlassian Crowd directory Changing this setting alone may be enough to resolve errors relating to directory permissions. The "Read/Write" radio button needs to be selected. "local-admin" in the built-in Internal Directory) and edit your external user directory's settings. Login via a different user directory (e.g. ![]() This applies to all directory types except Internal with LDAP authentication. ![]() When a external user directory is added to Confluence or Jira Software, it may be set to Read Only or Read/Write. Step 1 - Update user directory in Atlassian host application to Read/Write This is a limitation with Bitbucket itself. If you running User Management inside Bitbucket it is impossible to configure external directories as read/write.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |