Can not set security settings explicitly

Question

Hi,
I'm trying to create a workspace(library) and a folder via APIs and need the program NOT TO INHERIT security setting from the library to the sub folder.
Given below are my attribute for the workspace creation and folder creation respectively,
Attributes for the workspace:
NamedValue[] wsDef = WsUtility.newNamedValueArray(new Object[][] {
{ Attributes.NAME, workspaceName },
{ Attributes.DESCRIPTION, workspaceDesc },
{ Attributes.SECURITY_CONFIGURATION,
WsUtility.newNamedValueArray(new Object[][] {
{ Attributes.GRANTS, wsGrants }}) } });
Where wsGrants,
contains row with
NamedValue[] wsReaderGRPGrant = WsUtility.newNamedValueArray(new Object[][] {
{ Attributes.GRANTEE, attr[0].getValue()},
{ Attributes.ROLES, new long[] { readerRole.getId() }},
{Attributes.PROPAGATING, Boolean.FALSE}});
Attributes for the folder:
NamedValue[] fDef = WsUtility.newNamedValueArray(new Object[][] {
{ Attributes.NAME, folderName },
{ Attributes.DESCRIPTION, folderDesc},
{ Attributes.HAS_EXPLICIT_SECURITY_CONFIGURATION,Boolean.TRUE} });
With these setting, the sub folder still inherits security settings from the workspace.
Can anyone help me please?
Thanks,
Tenjuka

Answer 1

I haven't tried to create this sort of setup using code, yet. Some thoughts though...
In what order are you performing these steps? One of things I've observed is that when using the Content UI, when switching from Inherit to Modify, the base security configuration starts out the same as the parent. Are you still seeing the "inherit" switch set to on your subfolder?
Another thought, it would appear that you are setting each GRANT to be non-propagating for the user being added with the READER role to the workspace. This would imply that only accounts added in with this should not propagate to the folder that isn't inheriting. Are you seeing these additional readers?
Is the workspace security configuration set to CONFIGURATION_FINAL? Are you supplying a security configuration for the subfolder after providing the HAS_EXPLICIT_SECURITY_CONFIGURATION attribute for the folder? Perhaps the system doesn't like having a null security configuration when it's been instructed that there is one.