Issue Details (XML | Word | Printable)

Key: CONF-5453
Type: Support Request Support Request
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Don Willis [Atlassian]
Reporter: Andy Ciordia
Votes: 0
Watchers: 1
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
Confluence

Space with no administration rights won't allow addition of user/group

Created: 09/Feb/06 01:48 PM   Updated: 14/Feb/08 10:57 PM
Component/s: Users & Groups
Affects Version/s: 2.0.2
Fix Version/s: 2.6.0

Time Tracking:
Not Specified

File Attachments: None
Image Attachments:

1. confluence_grab.png
(98 kB)
Environment:
Version: 2.0.2 Build:#322 Dec 05, 2005
Java Version 1.5.0_06
Java Vendor Sun Microsystems Inc.
JVM Version 1.0
JVM Vendor Sun Microsystems Inc.
JVM Implementation Version 1.5.0_06-b05
Java Runtime Java(TM) 2 Runtime Environment, Standard Edition
Java VM Java HotSpot(TM) Client VM
Operating System Linux 2.4.21-32.0.1.ELsmp
Issue Links:
Duplicate
 
Reference
 

Participants: Andy Ciordia, Don Willis [Atlassian], Matt Ryall [Atlassian] and Mei Yan Chan [Atlassian]
Since last comment: 1 year, 16 weeks, 3 days ago
Company: pgdc.com (Find related issues)
Resolution Date: 09/Aug/07 01:36 AM
Labels:


 Description  « Hide
I've been upgrading confluence versions for a while now and didn't catch this permission error in the last round. As it stands (see graphic-attachment) there is anonymous access to the space but no users or groups, thusly no administrator. I'm triggering the fail-safe that should not allow the editing of perms in a space to null admin rights, but since I have somehow gone beyond it, it's acting as a trap keeping me from modifying the perms. I am the confluence administrator.

Somehow I need to push some user/admin into the group underneath the ui or theres a way around the ui within the ui.

Some guidence is appreciated,

-a



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Mei Yan Chan [Atlassian] added a comment - 20/Jun/07 04:16 AM
Hi Andy,

Would it be possible for you to restore the space and see if it resolves your problem? I believe you are still using Confluence 2.0.2, I would suggest that you upgrade to our latest version - 2.5.4, at the link below:

http://www.atlassian.com/software/confluence/ConfluenceDownloadCenter.jspa

If the above does not resolve your problem, please attach a zip backup of your <confluence-install>/logs to this issue.

In addition, for all future support requests, please raise an issue at:

https://support.atlassian.com

We simply use http://jira.atlassian.com for tracking bugs and feature requests/improvements. Thanks.

Regards,
Mei


Don Willis [Atlassian] added a comment - 21/Jun/07 03:07 AM
I wouldn't advise upgrading to 2.5.4 to fix this bug as it still exists, but as Mei suggests, support should be able to help you out.

Matt Ryall [Atlassian] added a comment - 23/Jul/07 09:10 PM
This problem occurs when the only users who had space admin rights are no longer valid users in an external user repository (e.g. LDAP). Due to the complexity of the issue, this is likely to only be fixed in Confluence 2.6, not on any prior stable release.

To workaround this problem where the only user with space admin permissions has disappeared:

  • First, try reactivating the user in LDAP. This should allow you to assign someone else admin permissions before disabling them again.
  • If this is not possible, you can modify the Confluence database to reassign the reassign the old user's ('olduser') permissions to an existing user ('newuser') in the database.

To do the latter, you need to:

1. Shutdown Confluence.
2. Back up your Confluence database.
3. Modify the database like this:

UPDATE SPACEPERMISSIONS SET PERMUSERNAME = 'newuser' WHERE PERMUSERNAME = 'olduser';

4. Start Confluence again.

Please ensure you backup your Confluence database before performing any modifications.


Don Willis [Atlassian] added a comment - 09/Aug/07 01:36 AM
Rewrote the space permissions action to apply the changes to the form, rather than try to make the state the same as on the form. The bug was caused by some permissions not making it to the form due to their invalidity.

The rewrite was essential to fix potential problems such as permissions being removed when an LDAP repository is temporarily inaccessible.