How do I restrict users from using the PrivateArk Client?
Steps
There are some use cases where it is not advantageous to use the PrivateArk Client, e.g., the creation of safes within the client does not grant access to the PVWAAppUsers, which can cause errors when trying to access accounts. Also, it may not be a good idea to allow end users the capability to use the PrivateArk Client.
To restrict access this is done through Directory Mapping. This example will restrict it for the Vault Users mapping:
-
Open the PrivateArk Client and log in as administrator
-
Navigate to Tools -> Administrative Tools -> Directory Mapping
-
Select the desired map (Vault Users Mapping)
-
Click "User Template"
-
Next to "User Type", select "Authorized Interfaces"
-
Use the arrows to move "WINCLIENT" to the list of "Available Interfaces"
The next time a user attempts to use the client, they will see an authentication failure. However, in the italog, you will see that WINCLIENT is not an authorized interface.
Q:
How do I restrict users from using the PrivateArk Client?
A:
There are some use cases where it is not advantageous to use the PrivateArk Client, for example creation of safes within the client does not grant access to the PVWAAppUsers, which can cause errors when trying to access accounts. Also it may not be a good idea to allow end users the capability to use the PrivateArk Client
To restrict access, this is done through Directory Mapping. This example will restrict it for the Vault Users mapping
1. Open the PrivateArk Client and log in as administrator
2. Navigate to Tools -> Administrative Tools -> Directory Mapping
3. Select the desired map (Vault Users Mapping)
4. Click "User Template"
5. Next to "User Type", select "Authorized Interfaces"
6. Use the arrows to move "WINCLIENT" to the list of "Available Interfaces"
The next time a user attempts to use the client, they will see an authentication failure. However in the italog, you will see that WINCLIENT is not an authorized interface