-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
When new users are created in Stash the directory cannot be chosen. To create a user in a specific directory the directory position must be changed. Since, the directory type cannot be chosen the password field is enabled when creating a user who belongs to a delegated directory.
Workaround:
If you are trying to create a user and assign it to "Delegated LDAP", place your directory as the first one on the "User Directory" list. Once you manually create a user in Stash, it will be automatically assigned to your delegated LDAP directory:
User Directory List:
Manually created user when Delegated LDAP is the first one on the list:
- is related to
-
BSERV-3424 Disable "Change password" field from admin and user page when delegated authentication is used
-
- Closed
-
-
-
- Closed
-
- relates to
-
- Closed
-
- Closed
-
- Gathering Interest
- is blocked by
-
EMBCWD-972 Loading...
- mentioned in
-
-
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[BSERV-3323] Cannot chose directory when creating user
Changing the directory order to workaround is not viable all the time. Will this be fixed sooner so user creation can be more seamless like other Atlassian products like Fish Eye?
The Rest api to create new user also need to improve to specify if the user needs to be created as 'built-in" vs LDAP
BitBucket rest as you can see here:
https://developer.atlassian.com/static/rest/bitbucket-server/4.0.0/bitbucket-rest.html#idp2099280
there is no way to specify directory, whereas for fisheye, it takes a user type (built-in or LDAP).
https://docs.atlassian.com/fisheye-crucible/3.6.2/wadl/fecru.html#rest-service-fecru:admin:users
Bradley Baetz
added a comment - This makes it difficult to create 'role' account users (eg for scripts using the rest API) when using delegated LDAP - I've had to change the directory order, add the user, and then change it back. (I know that oauth is supported, but username is simpler)
Bradley Baetz
added a comment - This makes it difficult to create 'role' account users (eg for scripts using the rest API) when using delegated LDAP - I've had to change the directory order, add the user, and then change it back. (I know that oauth is supported, but username is simpler) All users created through the Stash UI should be created in the internal directory
That's the issue here I think. There are 2 internal directories: the 'default' one with internal authentication and a second one with delegated authentication. The user would like the option to chose one of those internal directories when creating a user, regardless of the directory order.
And to avoid any kind of confusion, it would be nice to have the Create User screen mention a "user directory" field in any cases to make it clear where will the user be created.
According to the screenshots the atest user exists in the delegated directory.
All users created through the Stash UI should be created in the internal directory. This is by design and makes sense as Stash only allows read only remote directories. The ordering should only matter when you have a user with the same name in multiple directories. It can also affect performance of logging in.
As shown in the Screenshot "UserList" I have attached above the user "atest" was created while Stash internal directory was on top of the list and I could not log in because the user didn't exist in the delegated directory. So I moved the delegated directory to the top of the list as shown in the screenshot "User directories" and re-created the user again and managed to log in.
Due to the effort required and the existence of a workaround (even though it's not ideal), we are unlikely to address this issue. As a result, I'm closing this issue as "Won't Fix".