Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Delete Document setting broken on switch to LDAP

Status
Not open for further replies.

rbaylis

MIS
Jun 17, 2005
2
GB
We are implementing webi document reporting under 6.5 (repository is on MS SQL Server) and during development our security settings worked just fine.

Erring on the side of caution, options were locked down pretty tightly at the root level so regular users were constrained to opening, refreshing and exporting to Excel, and we had a 'power users' group ready to go if we decided to open up the functionality a bit after a settling in period. Developers and admin staff of course were in groups where the settings were opened up again to allow them to create and delete Corporate Documents.

Then we turned LDAP authentication on and discovered some downsides to that approach, with some functions going missing for users that previously had them.

Figuring the group based permissions weren't being resolved in exactly the same manner under LDAP, we turned the model upside down and started with everything enabled at the group level and locked it down only for the parent group containing our end users.

But we still can't get the "Delete other Users' Corporate Documents' setting to work at all now. No matter what we set it to (even if 'Hidden' across the entire security domain with no overrides anywhere), all users can delete any document, yet it was fine before we turned LDAP on.

I've raised a case with BO Support, but I wonder if this rang bells with anyone here, or you had any suggestions?
 
We found out what was happening, and BO Tech Support have confirmed it is a bug.

If anyone else has the same problem, make sure "Delete other Users' Corporate Documents" is set to 'Inherit' at the root level, then override it as required from there. If you use any other setting at the root, none of the overrides will cme into effect.

BTW, the default action that will be inherited is for the setting to be 'Hidden'.

The suspicion is that this bug also applies to the other setting expressed in the negative "Do Not Always Regenerate SQL".

All other settings work fine if you start with 'Enabled' and then override them - at least you can see the values that are being inherited from the Parent Group, which is why we went for this method. We just weren't expecting to encounter this bug with the negatively expressed conditions.

Hope that helps someone else tearing their hair out!

Richard Baylis
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top