27.12.2013 Views

SAS® Integration Technologies: Administrator's Guide (LDAP Version)

SAS® Integration Technologies: Administrator's Guide (LDAP Version)

SAS® Integration Technologies: Administrator's Guide (LDAP Version)

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>SAS®</strong> <strong>Integration</strong> <strong>Technologies</strong>: <strong>Administrator's</strong> <strong>Guide</strong> (<strong>LDAP</strong> <strong>Version</strong>)<br />

AclEntry<br />

The aclEntry attribute describes the access granted to the entry object. It describes who has rights (the subject), what<br />

rights they have to the object itself, and what rights they have to the attributes of the object. The format of the aclEntry<br />

attribute is:<br />

:::<br />

Subject−type<br />

SubjectDn<br />

Object−access<br />

Attribute−access<br />

one of access−id, group, or role. If access−id, then subjectDN should be the DN of a<br />

user entry. If group, subjectDN should be the DN of an AccessGroup entry, and role<br />

should point to an AccessRole entry.<br />

The Dn of the subject for the aclEntry.<br />

The access rights granted to the object itself. Valid permissions are a to allow the<br />

subject to add children under the entry, and d to allow delete permission. The format for<br />

object access is "object:permissions".<br />

Specifies the permissions granted to the entry attributes. There are three levels of<br />

attribute access: normal, sensitive, and critical. The security level for an attribute is<br />

defined in the schema.<br />

AclPropagate<br />

This attribute will have a value of "true" or "false". The default is "true", and indicates that the aclEntry values for this<br />

entry should propagate down the hierarchy to apply to any entries below it which don't have their own aclEntry<br />

attribute(s).<br />

EntryOwner<br />

Like the subject clause of the aclEntry, the entryOwner has a subject type and a subjectDN. The subject type can be<br />

access−id, group, or role. The subjectDN should be the distinguished name of an entity that represents the correct type<br />

of entry (person, accessGroup, or accessRole).<br />

Example: access−id:cn=SAS,o=SAS Institute,c=US<br />

OwnerPropogate<br />

A value of "true" or "false" that determines whether the entryOwner value will propogate to down the hierarchy to<br />

apply to entries below it.<br />

ACI Rule Considerations<br />

AclEntry attributes in SecureWay propogate down (assuming aclPropogate is true) to all its subordinates until the<br />

aclEntry is overridden. Any aclEntry will override all the values of the previous aclSource. That is to say, if you want<br />

to add access by another individual or group at a given point in the tree, while retaining the access controls specified<br />

higher up, you must copy the aclEntry attribute values that the entry is already inheriting, and add the new values. Just<br />

creating an aclEntry with the new value will revoke the access provided by the previous aclSource.<br />

SecureWay Directory Server Access Control Overview 239

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!