- Products
- Solutions
- Resources
- Trials
- Support
- Partners
- Communities
Hello,
I am relatively new to the ARS backend orchestration engine, so I'm not ensure if what I would like to achieve is possible. But here goes....
I am trying to use ARS to restrict group membership to specific types of users, using attributes. We have an integer attribute in our AD for groups named "custMemberIdType". Under policies, I have managed to create a policy to only accept one of 7 integers which would define one of the following user types (Validates the 'custMemberIDType' property values for 'Group' object)....
0 (-T1 Admins)
1 (-T1 Server Operators)
2 (-T1 Service Accounts)
3 (-T2 Admins)
4 (-T2 Device Operators)
5 (-T2 Service Accounts)
6 (-Generic Application Privileged Acct)
7 (-Normal Account) (Default)
What I would like to do is, when a user creates a new group, they are prompted to select a group type for the group, based on a friendly name (indicated above in brackets), rather than a cryptic number. So far, I can only get the list of integers to show in the GUI. Is there a way to map the friendly names above, to the integers for each type, used in the GUI and web client?
Regards,
Jay
To implement the method I mentioned previously (without using Administration Policy/Worksflow Scripts) I would do the following:
So we need to add the property to the appropriate forms within all the Active Roles Web Sites you need it to be present (ignore the colours of the ARWebAdmin site below, I’m in the middle of writing something…
Hi Jay
Use two VA, your existing 'custMemberIdType' and a new 'custMemberType'
In this scenario, you've have an Administration Policy which enforces that the new 'custMemberType' is populated, and the possible values (which would related to your T1 Admins, T1 Server Operators, T1 Service Accounts etc etc etc)
Then have a workflow which fires on change/set of custMemberType, which then triggers the existing 'custMemberIDType' property's value to be the number which associated with the value being set in 'custMemberType'
For the Web Page, you'd just show the 'custMemberType' property, not the ID... you'd also probably want something to set the custMemberType if the custMemberIDType changes... but be careful with this to, as you don't want one change triggering another, triggering another etc etc.
If you need more details, let me know.
To implement the method I mentioned previously (without using Administration Policy/Worksflow Scripts) I would do the following:
Friend Name |
Common Name |
Syntax |
Multi value |
Object Classes |
Stored |
custMemberIDType |
custMemberIDType |
Integar |
No |
Group |
Yes |
custMemberType |
custMemberType |
Case Ignore String |
No |
Group |
Yes |
Controlled Property |
Policy Rule |
custMemberIDType |
Must be specified |
Must be: · 7 (default) · 1 · 2 · 3 · 4 · 5 · 6
|
|
custMemberType |
Must be specified |
Must be: · Normal Account (default) · T1 Admins · T1 Server Operators · T1 Service Accounts · T2 Admins · T2 Device Operators · T2 Service Accounts · Generic Application Privileged Acct |
At this point we have 2 virtual attributes linked to a group object, where the custMemberType has to be one of the 8 values defined in the Administration Policy, which will default to “Normal Account” and custMemberIDType, which can be blank but defaults to 7. The policy object will look like:
The workflow will look something like:
Test the Administration Policies and Workflow by
There are other ways of doing this involving policy scripts, but the above will get you working.
Hey Stu.Pollock Thank you for the comprehensive response. I've just come back from vacation, so once I catch up on my inbox and tasks, I'll give this a shot and report back.
Many thanks!
Jay
@Stu.Pollock ... You are a godsend!... thank you for this information. I had to tweak your process a little, as custMemberIDType was already an attribute in our extended DS schema, but after that, your process worked flawlessly for the Full GUI.
Would have any pointer on this configuration working in the Web GUI too? Your opening message suggests just making the virtual attribute visible / available on the Web GUI. A quick search has me looking a VBCode and the like, but I wondered if you could suggest a starting point for this?
Warmest regards, and many thanks!
Jay
Adding the VA to the Web UI is relatively painless.
Make sure you are logged into the web UI as an Active Roles Admin. Then follow the procedure here:
support.oneidentity.com/.../26
So we need to add the property to the appropriate forms within all the Active Roles Web Sites you need it to be present (ignore the colours of the ARWebAdmin site below, I’m in the middle of writing something for a customer).
To test the change (in this example) create a new group that is in scope of the Administration Policy created in the previous instructions, and you should now see the Member Type entry created above is now present at the bottom on the General Properties tab of the New Group form
This entry you added to the form can be moved around, IE up and down on the General Properties tab, or you could move it to another tab (by deleting it from the general tab, clicking on the tab you want to put it in, then choosing Add Entry and clicking Select, then choosing the entry you created [in this instance ctr;l + f is your friend, you’ll need to scroll to the bottom of the page to click Finish, but then it’s the save as steps 11 and 12])
Stu.Pollock JohnnyQuest I never thanked you for taking the time to provide such detailed responses which helped absolutely in achieving the task.
Thank you both! I hugely appreciate the help you offered.
Jay