Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-7332

Delegated LDAP users should not be able to change email/display name when 'copy user on login' option is enabled

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Low Low
    • None
    • 3.6.1, 3.8.0
    • Enterprise, User Management - LDAP
    • None

    • Linux RHEL6, x86_64 (3.6.1)
      Fedora, x86)64 (3.8.0)

      When using a delegated LDAP directory, users are able to change their display name and email address in the 'manage account' section.

      There's no point to allowing this, and it just confuses people - the settings will be resynced when the user logs in again (STASH-2995).

      This only happens with delegated LDAP directories, not 'regular' ones.

      This is similar to STASH-2978 which fixed this issue for the password setting, but not the display name/email.

        1. Screenshot 2015-05-13 18.05.56.png
          242 kB
          Nick

            [BSERV-7332] Delegated LDAP users should not be able to change email/display name when 'copy user on login' option is enabled

            Brent P added a comment -

            We're incorporating the solution for this into STASH-2995.

            Brent P added a comment - We're incorporating the solution for this into STASH-2995 .

            Bradley Baetz added a comment -

            @npellow - I am using the 'copy user on login' option

            Bradley Baetz added a comment - @npellow - I am using the 'copy user on login' option

            Brent P added a comment -

            We shouldn't use the same solution to STASH-4514 here. The solution to STASH-4514 lets Crowd tell us "the user can't reset their password". The solution to this may be similar: ask Crowd if the user can update their name.

            Crowd do not want to expose the directory structure to us (and I think that's good), so we can't just ask "is this a delegated LDAP directory?"

            Brent P added a comment - We shouldn't use the same solution to STASH-4514 here. The solution to STASH-4514 lets Crowd tell us "the user can't reset their password". The solution to this may be similar: ask Crowd if the user can update their name. Crowd do not want to expose the directory structure to us (and I think that's good), so we can't just ask "is this a delegated LDAP directory?"

            Nick added a comment -

            To be clear: Is this only an issue when the "Copy users on login" checkbox is checked for that Delegated LDAP Directory ?

            Nick added a comment - To be clear: Is this only an issue when the "Copy users on login" checkbox is checked for that Delegated LDAP Directory ?

            Nick added a comment -

            Can we use the same functionality which was introduced as part of STASH-4514 to prevent users editing profile data which will be resynced from LDAP anyway?

            Nick added a comment - Can we use the same functionality which was introduced as part of STASH-4514 to prevent users editing profile data which will be resynced from LDAP anyway?

              Unassigned Unassigned
              06fbb7509c24 Bradley Baetz
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: