...
Request Detail | Example |
Date and time for change | January 1, 2010 |
Description of the port change | Allow all workstations of the Application Development group access to the Oracle database port |
Ingress/egress characteristic | Incoming on port 1521 |
Destination/source specification | Source: wk1.ucdavis.edu, wk2.ucdavis.edu, wk3.ucdavis.edu Destination: dbhost.ucdavis.edu |
The term of the change (indefinite or otherwise) | Indefinite |
Project related to the requested rule(s) change | Kuali Rice Implementation |
Create Users
Let's create an XML file that defines some users who will help us simulate the Request Firewall Change process. We have requester1 who will submit all requests and FPG1 & FPG2, who will be tasked with reviewing and approving (or disapproving) any Firewall Change requests.
Note: In the Kuali Rice production environment, users will be managed via the Identity Management system.
| Code Block | ||
|---|---|---|
| ||
<?xml version="1.0" encoding="UTF-8"?>
<data xmlns="ns:workflow" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="ns:workflow resource:WorkflowData">
<users xmlns="ns:workflow/User" xsi:schemaLocation="ns:workflow/User resource:User">
<user>
<workflowId>requester1</workflowId>
<emplId>requester1</emplId>
<authenticationId>requester1</authenticationId>
<uuId>requester1</uuId>
<emailAddress>requester1@ucdavis.edu</emailAddress>
<displayName>Requester One</displayName>
<givenName>Requester</givenName>
<lastName>One</lastName>
</user>
<user>
<workflowId>FPG1</workflowId>
<emplId>FPG1</emplId>
<authenticationId>FPG1</authenticationId>
<uuId>FPG1</uuId>
<emailAddress>FPG1@ucdavis.edu</emailAddress>
<displayName>Firewall Group Policy User One</displayName>
<givenName>Firewall Group Policy User</givenName>
<lastName>One</lastName>
</user>
<user>
<workflowId>FPG2</workflowId>
<emplId>FPG2</emplId>
<authenticationId>FPG2</authenticationId>
<uuId>FPG2</uuId>
<emailAddress>FPG2@ucdavis.edu</emailAddress>
<displayName>Firewall Group Policy User Two</displayName>
<givenName>Firewall Group Policy User</givenName>
<lastName>Two</lastName>
</user>
</users>
</data>
|
Create Workgroups
Here we create a workgroup called eDoc.FirewallPolicyGroup.Workgroup. Per our business process, all Firewall Change Requests will be routed to this group for review and approval. The users FPG1 and FPG2 are hereby inducted into this group.
Note 1: Just like users, workgroups will be managed via the Identity Management system in the Kuali Rice production environment.
Note 2: As more and more UCD departments use eDocLite, workgroup names will tend to become longer (i.e. eDoc.IET.DataCenter.FirewallPolicyGroup.Workgroup vs. eDoc.IET.Middleware.FirewallPolicyGroup.Workgroup vs. eDoc.ORMP.FacilitiesManagement.FMIS.FirewallPolicyGroup.Workgroup)
| Code Block | ||
|---|---|---|
| ||
<?xml version="1.0" encoding="UTF-8"?> <data xmlns="ns:workflow" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="ns:workflow resource:WorkflowData"> <workgroups xmlns="ns:workflow/Workgroup" xsi:schemaLocation="ns:workflow/Workgroup resource:Workgroup"> <workgroup> <workgroupName>eDoc.FirewallPolicyGroup.Workgroup</workgroupName> <description>Firewall Policy Group for Firewall Change Requests</description> <members> <authenticationId>FPG1</authenticationId> <authenticationId>FPG2</authenticationId> </members> </workgroup> </workgroups> </data> |
...