Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-28031

Provide a method for administrators to edit the remote user directory they are logged in from

XMLWordPrintable

    • 4
    • 8
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      At the present time, Confluence will not allow an administrator to edit the directory they are currently logged in from. For example, if logged into Confluence as a user from Crowd, the Crowd user directory will not be able to be modified. Normally we recommend logging in as the local Confluence admin in order to edit other directories.

      However, when Crowd SSO is enabled, only users from the Crowd user directory can authenticate. To get around this, administrators will need to edit the seraph-config.xml to use the default Confluence authenticator instead of the Crowd SSO authenticator and restart Confluence in order to log in as the local admin. The application will require another restart to re-enable SSO.

      This improvement request is to investigate if there's a better way to edit the Crowd user directory in Confluence when SSO is enabled.

      The same is true of IIS with NTLM.

            [CONFSERVER-28031] Provide a method for administrators to edit the remote user directory they are logged in from

            Frank Duerr added a comment -

            Jenny (Inactive) added a comment - 29/Oct/2018 12:55 AM
            Thanks for your interest in this issue.
            This request is considered a potential addition to our longer-term roadmap.
            We'll typically review this request at least once a year, at which point we’ll consider whether we need to alter its status. 
            Best,
            Confluence Product Management

             

            Looks like we have different understandings of "longer-term"...
            The ticket is 10 and the aforementioned comment is about 6 years old. Even the employee who wrote the comment has probably left Atlassian in the meantime . I am very disappointed.

            Frank Duerr added a comment - Jenny (Inactive) added a comment - 29/Oct/2018 12:55 AM Thanks for your interest in this issue. This request is considered a potential addition to our longer-term roadmap. We'll typically review this request at least once a year, at which point we’ll consider whether we need to alter its status.  Best, Confluence Product Management   Looks like we have different understandings of "longer-term"... The ticket is 10 and the aforementioned comment is about 6 years old. Even the employee who wrote the comment has probably left Atlassian in the meantime . I am very disappointed.

            ChristianMoserMTF added a comment - - edited

            >  This is infuriating, and makes me want to sent a glitter bomb to Atlassian's developers.

            me too.

            I'd be interested to know how far you had to go to get Atlassian to fix something. The much money you have to pay for Confluence is obviously not enough... 

            ChristianMoserMTF added a comment - - edited >  This is infuriating, and makes me want to sent a glitter bomb to Atlassian's developers. me too. I'd be interested to know how far you had to go to get Atlassian to fix something. The much money you have to pay for Confluence is obviously not enough... 

            Jenny (Inactive) added a comment -

            Thanks for your interest in this issue.

            This request is considered a potential addition to our longer-term roadmap.

            We'll typically review this request at least once a year, at which point we’ll consider whether we need to alter its status. 

            Best,

            Confluence Product Management

            Jenny (Inactive) added a comment - Thanks for your interest in this issue. This request is considered a potential addition to our longer-term roadmap. We'll typically review this request at least once a year, at which point we’ll consider whether we need to alter its status.  Best, Confluence Product Management

            Dr. Lutz Wohlrab added a comment -

            Please fix this. It is causing unneccessary maintenance windows, preventing Jira and Confluence being handled the modern way - maintenance without downtime. Affects 500 users at our installation.

            Dr. Lutz Wohlrab added a comment - Please fix this. It is causing unneccessary maintenance windows, preventing Jira and Confluence being handled the modern way - maintenance without downtime. Affects 500 users at our installation.

            Paul Mansfield added a comment -

            please please fix this.

            We updated our internal self-signed certificate on our crowd server and needed to switch the URL across all our estate. It's easy to change Bitbucket and crucible, you can login as local admin, edit the URL for crowd, and most importantly, TEST it, and then commit the change.

            Bamboo nearly does this. I tried this with Bamboo, and Bamboo server crashed! I had to force a shutdown by killing the processes! Major panic! Fortunately it started up normally, and the edit of the crowd URL had made it into the config.

             

            With JIRA and confluence, you have to shut them down, turn off Crowd authentication, then you can login as local user, edit the URL, and then shutdown and turn Crowd auth back on. This is infuriating, and makes me want to sent a glitter bomb to Atlassian's developers.

             

            Paul Mansfield added a comment - please please fix this. We updated our internal self-signed certificate on our crowd server and needed to switch the URL across all our estate. It's easy to change Bitbucket and crucible, you can login as local admin, edit the URL for crowd, and most importantly , TEST it, and then commit the change. Bamboo nearly does this. I tried this with Bamboo, and Bamboo server crashed! I had to force a shutdown by killing the processes! Major panic! Fortunately it started up normally, and the edit of the crowd URL had made it into the config.   With JIRA and confluence, you have to shut them down, turn off Crowd authentication, then you can login as local user, edit the URL, and then shutdown and turn Crowd auth back on. This is infuriating, and makes me want to sent a glitter bomb to Atlassian's developers.  

            Xabier Davila added a comment -

            I've just been bitten by this one. Can you provide an update?

            Xabier Davila added a comment - I've just been bitten by this one. Can you provide an update?

            Kumaran added a comment -

            This feature would be really helpful to our organization. An update to this request is much appreciated.

            Kumaran added a comment - This feature would be really helpful to our organization. An update to this request is much appreciated.

            Uhub Admin added a comment -

            Much needed feature for people using Crowd + Confluence/JIRA.

            We have found a way around this which is to have the application's local account enabled in Crowd with the same details (username/password). Somehow the 2 accounts are consolidated into the local application account, hence allowing login as a local user to the application, which will allow us to disable the remote directory without having to disable SSO and restart Confluence/JIRA.

            Uhub Admin added a comment - Much needed feature for people using Crowd + Confluence/JIRA. We have found a way around this which is to have the application's local account enabled in Crowd with the same details (username/password). Somehow the 2 accounts are consolidated into the local application account, hence allowing login as a local user to the application, which will allow us to disable the remote directory without having to disable SSO and restart Confluence/JIRA.

            Fusion Helpdesk added a comment -

            This is making me lean towards getting rid of Crowd as its a single point of failure for all the applications.

            Fusion Helpdesk added a comment - This is making me lean towards getting rid of Crowd as its a single point of failure for all the applications.

            Krisjanis Morkans added a comment - - edited

            Spent too much time wandering what the hell is going on.
            PITA to recover if Crowd goes down.
            Also affects Jira.

            Krisjanis Morkans added a comment - - edited Spent too much time wandering what the hell is going on. PITA to recover if Crowd goes down. Also affects Jira.

              Unassigned Unassigned
              rchang Robert Chang
              Votes:
              119 Vote for this issue
              Watchers:
              70 Start watching this issue

                Created:
                Updated: