Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 22 Next »

Summary

The Request By Attribute process allows a department administrator to request protected actions in the Austin Active Directory by crafting the request as a JSON string then adding the request to an attribute on the department's Administrative organizational unit (OU).

Overview

The Request By Attribute process is comprised of the following parts: the request string, the requests attribute, the request script, the result string, the results attribute.

  • A request string is a JSON string that contains the required properties and values for the request. A department administrator creates the JSON string manually or via a PowerShell script published by the Active Directory team.
  • The requests attribute is a multi-valued attribute on a department's Administrative OU. A department administrator adds the request string to the requests attribute to submit the request. The attribute can contain multiple request strings.
  • The request process is the script that processes requests and the scheduled task that runs the script hourly. The request process removes the request string from the requests attribute when processing the request.
  • A result string is a JSON string that contains the results of processing the request along with the original request string. The request process creates the result string and appends any errors encountered during processing to the result string.
  • The results attribute is a multi-valued attribute on a department's Administrative OU. The request process adds the result string to the results attribute to report the outcome of the request to the department.

Organizational Units

The Request By Attribute process is centered around each department's Adminstrative OU. The Administrative OU for a department is the OU that contains the resources managed by the Department User Tools such as department user accounts and the department's Department Adminstrators group.

  • The distinguished name of the Administative OU for the EXAMPLE department would be: OU=EXAMPLE,OU=Departments,OU=Administrative,DC=austin,DC=utexas,DC=edu
  • The name of the Department Administrators group for the EXAMPLE department would be: EXAMPLE-Administrators

Attributes

The Request By Attribute process relies upon the security of the attributes on each department's Administrative OU object. The attributes are confidential and cannot be accessed by default. Access to the attributes has been granted to the request process and each department's Department Administrators group.

The specific attributes and the permissions granted to the attributes are as follows:

  • The requests attribute is the utexasEduAustinMulti1 attribute on a department's Administrative OU. The associated department's Department Adminstrators can read and write to this attribute submit requests.
  • The results attribute is the utexasEduAustinMulti2 attribute on a department's Administrative OU. The associated department's Department Adminstrators can read this attribute to review the results of any processed requests.

Supported requests

The Request By Attribute process supports the following request types:

  • Delegations - Department administrators can request changes to permissions on organizational units within a department. This process has previously been available only via a ServiceNow request.

Planned requests

The Request By Attribute process is expected to support the following request types in the future:

  • DNS - Department administrators can request changes to DNS records associated with the department. 


  • No labels