[RTFACT-17161] LDAP users added in Artifactory should be able to update their user profile (add SSH keys) Created: 23/Jul/18  Updated: 09/Mar/19

Status: Open
Project: Artifactory Binary Repository
Component/s: LDAP
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Normal
Reporter: Nihal Reddy Chinna Choudhary Assignee: Unassigned
Resolution: Unresolved Votes: 3
Labels: None

Issue Links:
Relationship
relates to RTFACT-16145 internalPasswordDisabled will change ... Resolved

 Description   

Currently when you login via LDAP to Artifactory, the user is added to a Group which has Admin privileges or a Group without Admin privileges. However in both the cases, the user is not able to get an option to add SSH keys to his profile page. The user is able to unlock the profile and generate API key and encrypted password, but cannot update their SSH keys.

For this test we have made sure that "Allow Created Users Access To Profile Page" is always enabled in the LDAP settings page.

Once this happens it is also not possible to Edit the user and manually enable the "Can Update Profile" option. 

The expected behavior is that the LDAP User should be able to update their user profile page and if needed add the SSH keys to their User.

 

Current Workaround which involves manual steps:

  1. Remove user from the LDAP admin group.
  2. Login to Artifactory which will update the User groups.
  3. Now you will be able to Check "Can Update Profile" checkbox in the Edit user page.
    https://<host>/artifactory/webapp/#/admin/security/users/<username>/edit
  4. The user can now enter an SSH key in their profile:
    https://<host>/artifactory/webapp/#/profile
  5. Add the user back to the LDAP admin group.


 Comments   
Comment by Chris Zardis [ 22/Feb/19 ]

I would argue this is a bug, and a frustrating one at that...

Please could it be addressed, so our users can add their own SSH keys via the UI?

Comment by Chris Zardis [ 22/Feb/19 ]

Please note this is not limited to LDAP - we just tested adding a new user via SAML and it has the same problem

Generated at Sat Apr 04 12:13:10 UTC 2020 using JIRA 7.6.16#76018-sha1:9ed376192612a49536ac834c64177a0fed6290f5.