Hello!
2 questions today:
1) I have created a separate webgui for our HR department. http://<adaxesserver>/HR. They have two actions available, one for creating a new user, and one for setting expiry dates for current users. How can I create an enforcement rule which will only apply to this webgui/these actions?
The only way I have been able to do this now is to create a generic business rule which applies before creating/updating users, with only one action: Require Approval. However, this rule will obviously apply to every create/update action that I do in Adaxes, regardless of which web gui I am working in, so I will need another method of enforcing approval.
2) With my current (flawed) method of enforcing approval, I noticed that when they reach the "This operation requires approval" page, the page also lists all users in the OU which they are allowed to administer, and they can view/modify most of the information. IMHO, this summary page should not contain this user browser part.
I have removed basically every "Display" and "Browse" option in the web gui management tool for this particular "/HR" subsite, but still, this user browser shows up on the "Requires Approval" page. The accounts who are able to log in to this site, has the common permissions "Create, delete and manage user accounts", which I believe I cannot restrict further, since they should be able to create new users, and be able to select users from a list and set expiry dates.
