Self-Service: Active Privilege Accesses
Self-Service: Active Privilege Accesses
Self-Service: Activate Privilege Accesses
In this article is described how user can activate existing privilege account and related accesses, which user is allowed to use.
This use case is part of Manage Privilege Access use case, and it needs to be implemented simultaneously.

Use Case Description
This use case is available only for IGA Enterprise package.
Please notice, that managing Administration level accesses for example in AD, it needs domain admin level permissions to the service account, which IGA solution is using for writing data towards AD.
| Description | |
Overview |
This use case describes how users can activate privilege account and accesses (which user is pre-defined to be allowed to use) from the Self-Service Portal. |
Operators |
IGA solution |
Prerequisites |
User needs to have privilege account and permissions to activate related IGA Entitlements (privilege accesses). Manage Privilege Accesses use case and all related uses cases are implemented. |
Result |
User privilege account is enabled for temporary time of period, group memberships is provisioned automatically to the directory or application and after maximum validation days account is disabled and group membership connections are removed. User is able to sign in with the privilege account. |
Operating chain |
|
Related datacards |
IGA Identity Storage |
Self-Service Portal services |
Activate Privilege Accesses |
Configuration Changes
Customer can define these configuration changes, without them affecting the projects schedule or work estimations.
1. Customer can define reasons and mandatory justifications
DeleteExpansion Possibilities
In this chapter are listed expansion possibilities, but please notice that these might have affect to the projects schedule and work estimations, so these will always needs Efecte Consultants review before agreeing on implementation.
1. Customer can also define, that activation is not needed for privilege accounts, but instead they are always active and privilege accesses (IGA Entitlements) are connected. This means that privilege account and accesses are always active and user can use them without any justifications.
This changes also use cases, "Request Privilege Account", "Request Privilege Accesses" and "Manage Privilege Accesses".
DeleteRelations and Configuration instructions
Relations to other use cases,
Relations to other data cards,
Configuration instructions:
- Publish service "Activate Privileged Accesses" in ESS
- Configure EPEtask called "[Directory] IGA Service request: Activate account"
- Configure the connection settings and after that Test connection from the EPEtask
- Define user and group filters and settings
- No need to change user identity mappings
- Go to IGA service request and workflow called "IGA Privileged Accesses"
- Check the workflow node Activate Account is it using right data source
- Check the workflow node Reset Password is it using right data source
- Publish the workflow
System test instructions:
- Test Activate Privileged Accesses from ESS
- Test user for this test case must have a privileged account and permissions to activate related IGA Entitlements
- Check the IGA Service request from ESM that is successfully handled
- Check from Directory that Privileged Account is activated
- Check from ESM that Privileged Account status is active
Delete