Self serve access flows grant access to a resource based on a user request for a defined time period.
This access flow type is best used for sensitive or highly regulated resources, such as access to production. It also suits just-in-time (JIT) or break-glass access cases.
To create a self serve access flow, you must define the permitted requestors, available resources, and approvers.
Follow these steps to define the permitted requestors:
On the Access Flows page, click Create Access Flow. The Create Access Flow page appears.
(Optional) Configure Settings.
Click Self Serve. The Self Serve fields appear below.
Enter an alphanumeric, user-friendly Access Flow Name.
Click When. A settings window appears to set the access period.
Set the access period.\
Click Select attribute to select an IdP attribute, such as User or Group.
(Optional) Click is to select conditional logic from the menu options.
Other operators include the following:
Is not
Contains
Does not contain
Starts with
Click Select value to select one or multiple users or groups from the menu options. This selection determines who is permitted to request access.
(Optional) Add another condition.
Under the last listed requestor, click +. A new row appears.
Repeat steps 7-10.
Select the conditional logic for the multiple requestors.\
You can define access to specific resources in an Apono integration.
Follow these step to define access to specific resources:
Under They will have access to, click Select target > Integrations.
Select an integration. The Select resource type panel appears.
Select the resource type.
Click Done. The panel closes.
Click permissions. The Permissions menu appears.
Select one or more permissions to grant the requester.
(Optional) Refine the available resources:
Click in the populated to field. A list of resources appears.
Select one or several resources.
By default, the user has access to Any resources. However, the following options allow you to define access more granularly:
Any resources except specific
Select by name
Select by tags
(Optional) Add another target:
Click + at the end of the row. A new target row appears.
Repeat steps 1-7.
You can define access to a specific bundle.
Follow these steps to define access to a specific bundle:
Click Select target > Bundles.
Select a bundle.
(Optional) To add another bundle, click +. A new target row appears.
Repeat steps 1-2.
Follow these steps to define the duration of access:
Click in the populated Grant for field. The granting period settings appear.\
Click Automatic to select the approval type.\
Click Create Access Flow.
Approval of provides in-depth options to customize the approval flow. This approval type is ideal for production environments and highly sensitive resources.
Follow these steps to set up Approval of:
Click the populated with field. The approval type menu appears.
Click Approval of. The Approval of fields appear.
Click Select attribute to select an IdP attribute, such as User, Group, or Owner.
If you have connected an incident response integration with Apono, the attribute can also be an on-call shift.
(Optional) Click is to select conditional logic from the menu options.
Other operators include the following:
Is not
Contains
Does not contain
Starts with
Click Select value to select one or multiple users or groups from the menu options. This selection determines who is permitted to approve access.
(Optional) Add another approver condition.
Immediately beneath the last list approver, click +. A new row appears.
Repeat steps 3-5 to add another approver to the group.
Select the conditional logic for the multiple approvers.\
(Optional) Add another approver group.
Beneath the last approver group, click +. A new approval group appears.
Repeat steps 3-6 to add another approver to the group.
Select the conditional logic for the multiple groups of approvers.\
Item | Description |
---|---|
Period | Description |
---|---|
Condition | Description |
---|---|
Period | Description |
---|---|
Period | Description |
---|---|
Condition | Description |
---|---|
Condition | Description |
---|---|
Cloud resources
One or more resources in a cloud platform that has been integrated with Apono If you have not already, integrate Apono with a cloud platform to control access to its resources:
Apono identities
One or more identity sources in the Apono system There are various ways to add identities to Apono:
Always
(Default) Applies to the requester conditions at all times Follow this step to set this period:
Select Always.
Only on
Applies to the requester conditions during a specific time frame Follow these steps to set a specific period:
In the settings window, select Only on.
Select one or more days of the week.
In the From field, select a start time from the dropdown menu.
In the to field, select an end time from the dropdown menu.
Select a timezone from the dropdown menu.
AND
(Default) Allows the user to request access if they meet all the attributes of the user group
OR
Allows the user to request access if they meet any of the attributes of the user group
Custom
(Default) Grants the requester access for a custom period The default granting period is set to 1 hour. Follow these steps to grant access for a custom period:
Select the first radio button.
From the right dropdown menu, select a time unit.
In the first field, enter a numerical value for the time unit.
In the second field, select a time unit from the dropdown menu.
Indefinite
Grants the requester access indefinitely Follow this step to set this period:
Click Indefinite.
Automatic
Automatically grants the requester access for the specified period Automatic approval is the default setting.
Approval of
Grants the requester access for the specified period upon the approval of certain parties For more information, learn how to set up custom approval.
AND
(Default) If you have multiple attributes in the approval group, AND requires the approver to meet all the attributes.
OR
If you have multiple attributes in the approval group, OR requires the approver to meet only one of the attributes.
ANY OF
If you have multiple approval groups, ANY OF only requires one approver belonging to any group to approve access.
ALL OF
If you have multiple approval groups, ALL OF requires one approver per group to approve access.