Identity Governance ENUM Values: Technical Reference
Identity Governance ENUM Values: Technical Reference
1 Introduction .................................................................................................................................................................. 7
2.4 Potential SoD violation approval task delete reason type (ENUM: PsodvTaskDeleteReason) ............................ 8
3 Applications ................................................................................................................................................................. 9
5 Authorization.............................................................................................................................................................. 12
Technical Reference 2
7.1 Certification policy status (ENUM: CertificationPolicyStatus)............................................................................. 16
Technical Reference 3
11.4 Feed generation type (ENUM: FeedGenerationType) ....................................................................................... 26
12 Maintenance .............................................................................................................................................................. 27
13 Miscellaneous ............................................................................................................................................................ 30
Technical Reference 4
15 Reviews ..................................................................................................................................................................... 37
17.6 Technical role and SoD detection status (ENUM: DetectionStatus) .................................................................. 46
Technical Reference 5
17.7 Technical role approval state (ENUM: PolicyState) ........................................................................................... 47
Technical Reference 6
1 Introduction
This technical reference provides description of the internal ENUM values from the database that might appear in the
exported CSVs. Sections are in alphabetic order and sub-sections within each section are also arranged alphabetically.
2 Access Requests
This section documents ENUMs associated with access requests, access request and approval policies, and change
requests. A number of these ENUMs are used in other areas as well, but they are documented here as these are the
primary place they are used.
Technical Reference 7
Database table reference: ALLOWED_ITEM_REQUESTER.REQUESTER_TYPE
2.4 Potential SoD violation approval task delete reason type (ENUM:
PsodvTaskDeleteReason)
Reasons that potential Sod violation approval tasks are deleted.
• SOD_POLICY_DELETED – The SoD policy associated with the approval task was deleted.
• SOD_POLICY_DEACTIVATED – The SoD policy associated with the approval task was deactivated.
• SOD_POLICY_CHANGED – The SoD policy associated with the approval task changed.
• TENTATIVE_APPROVED – Item has been approved, but decision is not yet final.
• TENTATIVE_DENIED – Item has been denied, but decision is not yet final.
• TENTATIVE_RETRACTED – Item has been marked as retracted. It will ultimately be changed to RETRACTED.
We only use this state internally so that we know to create the necessary approval step records when the step is
finished. Unlike the TENTATIVE_APPROVED and TENTATIVE_DENIED states, this state cannot be undone.
Technical Reference 8
• DENIED – Item has been marked as denied. Decision is final.
• CLEARED – Item has been cleared to move ahead to the next phase after all potential SoD violation approvals it
is part of are completed. The next phase will be either approval or fulfillment phases.
3 Applications
This section documents ENUMs associated with applications.
Technical Reference 9
• IDM – IDM application.
• USD – US dollar.
• UNDEFINED – Undefined.
Technical Reference 10
• CORPORATE – Corporate license.
4 Attribute Definition
This section documents ENUMs associated with attribute definitions.
• STRING - String
• BOOLEAN – Boolean
• DATE – Date
• LOCALE – Locale
• COMPOSITE - Composite
Technical Reference 11
Database table references: ATTRIBUTE_DEFINITION.ATTRIBUTE_TYPE
• DERIVED – Attribute is derived, meaning it is collected and has a specific mapping, join rule that will be resolved
after collection.
• TRANSIENT – Attribute holds a calculated transient value that is not stored in the database.
5 Authorization
This section documents ENUMs associated with authorization features.
Database table references: AUTH_PERMISSION.AUTH_PERM_TYPE NOTE: The values in these columns are the
ordinal value of the enum, not the string value. The ordinal value is shown below with each enum.
Database table references: AUTH_ROLE.ROLE_TYPE NOTE: The values in these columns are the ordinal value of the
enum, not the string value. The ordinal value is shown below with each enum.
• RUNTIME (1) – Runtime authorization role – assigned when user matches specified criteria.
Technical Reference 12
• ADM – Global administrator.
• RA – Review administrator.
• DA – Data administrator.
• PA – Provisioning administrator.
• SO – Security officer.
• AU – Auditor
• RT_RV – Reviewer.
Technical Reference 13
• ARA – Access request administrator.
Database table references: AUTH_SCOPE.SCOPE_TYPE. NOTE: The values in these columns are the ordinal value of
the enum, not the string value. The ordinal value is shown below with each enum.
Technical Reference 14
Database table reference: APPROVAL_POLICY.TYPE
• DRAFT – The assigned approval policy requires approval and the administrator has not submitted the changes
for approval.
• PENDING_APPROVAL – Pending changes are ready for approval by the approver specified in the approval
policy.
• APPROVED – The approver approved the business role, but the business role has not yet been published.
• PUBLISHED - Business role is approved and the administrator has published the role.
• ARCHIVE – Business role has been deleted or a newer version has been created.
• MINED - The mining process created the business role and the administrators must promote it before they or
others can approve (depending on the approval policy) and publish it.
Technical Reference 15
BUSINESS_ROLE_INCL_ITEM.ITEM_TYPE, USER_RESOURCE.RESOURCE_TYPE,
USER_RESOURCE_CHECK.RESOURCE_TYPE
• NOT_CERTIFIED – Some entities covered by the certification policy are not reviewed.
• CERTIFIED – All entities covered by the certification policy are completely reviewed.
• NO_DECISION – Review is certified, review item does not have a final decision.
• NOT_REVIEWED – Review item is in the target criteria, but is not covered by any of the review instances.
• REVIEW_IN_PROGRESS – Review is in the target criteria, but is not covered by any of the review instances
and a review instance is in progress now.
Technical Reference 16
• ANY_DECISION – Only used internally – review item with ANY decision.
• NO_DECISION_REVIEW_IN_PROGRESS – Review instance is in progress and the item was reviewed before
with no final decision.
Technical Reference 17
8 Change Requests and Fulfillment
This section documents ENUMs associated with change requests and fulfillment processes. Many of these are also used
in access request processes.
• REFUSED – Fulfiller chose to not fulfill this request, instead left permission as is
• INITIALIZED – The change request item is created and provisioning has not been initiated
• VERIFIED – Provisioning changes in the application for the change item has been successfully verified
• NOT_ VERIFIED – Provisioning changes in the application for the change item has not been successfully
verified
Technical Reference 18
8.3 Change request type (ENUM: ChangeRequestType)
Change request types.
Technical Reference 19
• DAAS - Fulfilled by DaaS fulfillment target, examples are Service Now, BMC Remedy, edir or AD LDAP
fulfillment, generic REST/SOAP
• INITIALIZED – Change set has been generated for the provisioning to start.
• PENDING – Workflow process has been started and waiting for completion.
• AUTO – Auto provisioning – only applicable for change requests on permissions assigned via IDM.
• MANUAL – Manual provisioning is used for systems which require administrative intervention to complete
change requests.
Technical Reference 20
9 Collectors and Collector Templates
This section documents ENUMs associated with collectors and collector templates.
Technical Reference 21
• CREATED – Template creation event.
Technical Reference 22
Database table references: DATA_PRODUCER.DATA_PRODUCER_TYPE,
DATA_PRODUCTION.DATA_PRODUCER_TYPE
• MORTICIAN – Producer that is assigned to entities which are moved to the graveyard.
Technical Reference 23
• TRANSFORM_TRANSFORM_ERROR – Entity transformation failed in transforming the collected entity.
Technical Reference 24
10.5 Data production status (ENUM: CollectionStatus)
Statuses for data productions.
• BULK_DETECTION – Production is part of a bulk production. This production is not yet running. It will be
performed by another pending production.
• INLINE – Execute curation inline with the thread that created the curation.
Technical Reference 25
• ALTERED – Entity was altered.
• INFO – Information
• NONMATCHING_DRIVER_ID – The permission or account driver ID value does not match the driver ID of the
collected provisioning application.
• NONMATCHING_LOGICAL_ID – The permission or account driver ID value is valid, but the logical ID value
does not match the logical ID of the collected provisioning application.
Technical Reference 26
• NONMATCHING_UNIQUE_ID – Unification paired a collected user with an existing unique user ID to a
published user with a different unique user ID. This means that the unification results were different than some
previous unification.
• MULTIPLE_MATCHES – Unification paired a collected user with more than one published user.
• UNMATCHED_BUT_SAME_UNIQUE_ID – Unification did NOT pair a collected user with a published user with
the same unique user ID. This indicates that the collected user used to unify, but no longer does.
• MERGEABLE – Identities can be merged with identities from other mergeable identity data sources as specified
by join attributes.
• UNIQUE – Identities will not be merged with identities from other identity data sources.
12 Maintenance
This section documents ENUMs associated with maintenance activities – archiving, cleanup, etc.
Technical Reference 27
• DISABLE – Task was to disable archiving.
Technical Reference 28
Database table references: CLEANUP.CURR_ENTITY_TYPE, CLEANUP_ENTITY.ENTITY_TYPE,
CLEANUP_ENTITY_ITEM.ENTITY_TYPE
• SNAPSHOT – Snapshots
• ENTITY_CATEGORY – Categories
Technical Reference 29
• REMEDIATION_RUN – Remediation runs
13 Miscellaneous
This section documents miscellaneous ENUMs that do not fit nicely in any other category.
• IMPLICIT (1) – Implicitly assigned via membership in a group, container, provisioning role or other grouping.
Technical Reference 30
• APPLICATION – Application data source.
Database table reference: Many tables have an ENTITY_TYPE column or something similar to specify an entity type.
• USER – User.
• GROUP – Group.
• ACCOUNT – Account.
• PERMISSION – Permission.
• APPLICATION – Application.
Technical Reference 31
• CHANGE_REQUEST_ITEM – Change request item.
• TAG – Tag.
• SCHEDULE – Schedule
• ANALYTICS – Analytics.
• LICENSE – License.
Technical Reference 32
• ANALYTICS_DASHBOARD – Analytics dashboard.
• AUTHORIZATION – Authorization.
• REMEDIATION – Remedation
Technical Reference 33
• REVIEW – Review.
• INITIALIZING – Job has been created, but is not yet running – still pending.
Technical Reference 34
13.11 Snapshot status (ENUM: SnapshotStatus)
Status of a snapshot.
• MILLIS - Milliseconds
• SECONDS – Seconds
• MINUTES – Minutes
• HOURS – Hours
• DAYS – Days
• WEEKS – Weeks
• MONTHS – Months
Technical Reference 35
• YEARS – Years
14 Notification Templates
This section documents ENUMs associated with notification templates.
• REVIEW - Review.
• FULFILLMENT – Fulfillment.
• REMEDIATION – Remediation.
Technical Reference 36
• INACTIVE – Template is inactive.
15 Reviews
This section documents ENUMs associated with review definitions and review instances.
Technical Reference 37
Database table reference: REVIEW_ITEM.FINAL_DECISION
• APPROVAL_PROCESSED - Approval has been process by provisioning service. This can be a terminal state
• APPROVAL_PROCESS_ERROR - There was an error processing the review item by the provisioning service.
This can be a terminal state
• PERMISSION - Permission
• ACCOUNT - Account
Technical Reference 38
15.6 Review notification event (ENUM: ReviewNotificationEvent)
Review notification events. Defines review events which will cause notifications to be sent out.
• AUTO - Partial approval is completed automatically when review item completes it's reviewer cycle
Technical Reference 39
• SCHEDULE – Review was started by a job schedule as defined in the review definition.
• STARTING - Review is in the process of being started to either a PREVIEW or RUNNING state, formerly
INITIALIZED in 2.5 and below
• PREVIEW - Review is in preview stage, emails have not been sent, visibility is limited to review administrator.
• RUNNING - WF process has started, emails sent and review is officially running and visible to review owner and
reviewer(s).
• CERTIFYING - Waiting on Review Owner for certification decisions. Review owner can override and resolve
conflicts in this state.
• COMPLETE - This is a temporal state used for completing a review as is, a review instance record in the DB will
never have this status.
• PARTIAL_APPROVE - This is a temporal state used for partial completion of review items (and send to
fulfillment), a review instance record in the DB will never have this status.
• CANCELED - Canceled/Terminated.
• CRITERIA_SPEC – Targets are specified with criteria. The criteria is specified as JSON.
• LINKED_ENTITIES – Targets are specified as a list of entities, using their unique ID or ID. The list is specified
as JSON.
Technical Reference 40
15.11 Review target type (ENUM: ReviewTargetType)
Review target types..
The following review types are used functionally to supercede a subset of settings defined in the originating review
definition. They are referenced by a running review instance (review_instance.staged_review_definition_id). It is
important that the original review definition settings are still used, these are only a subset allowed by feature function.
• MICRO_CERT - Settings overriden by external policy to start a micro certification using normal target spec
• MICRO_CERT_DATA - Settings overriden by external policy to start a micro certification, with custom data linked
to suser, saccount, spermission, etc.
Technical Reference 41
• PENDING - No decision has been made yet
• MODIFY_ENTITY - modify entity applicable to user profile and business role definition review
• CONFIRM_MODIFY_SUPERVISOR - secondary reviewer(s) confirmed the change supervisor change from the
initial reviewer
• SKIP_KEEP - secondary reviewer skipped because initial reviewer kept item, based on policy defined on review
definition
• SKIP_REMOVE- - secondary reviewer skipped because initial reviewer removed item, based on policy defined
on review definition
• PENDING - Not in reviewer's queue yet. Only applicable for serial reviews
• ESCALATED - reviewer item was esclated to next reviewer because of time out
Technical Reference 42
• CANCELED - item cancelled, review terminated
• APPLICATION_OWNER - application owner(s), only applicable for accounts and or permission items
• EO - Escalation owner/reviewer
• RO - review owner
• NOT_ALLOWED – Do not allow self review in any form. Self review violations will be escalated at start, or not
allowed.
Technical Reference 43
• ALLOWED_ALL – Allow self review in all stages of review.
• LIMITED_MULTI – Self reviewer can see items when they are part of a multiple reviewer queue. Otherwise
violation will be escalated at review start, or not allowed.
16 Risk Calculation
This section documents ENUMs associated with risk calculation processes.
• AVG - Average.
• MAX - Maximum
Technical Reference 44
16.4 Risk score type (ENUM: RiskScoreType)
Risk score types.
• CLOSED – SoD violation was closed, most likely because it no longer is a violation.
• PERMS_OR_ROLES_REMOVED – Permissions or technical roles in the SoD policy were removed, either from
the user or from the catalog.
Technical Reference 45
Database table reference: SOD_CASE.PRE_HOLD_STATE, SOD_CASE.STATE, SOD_CASE_INFO.STATE
• ON_HOLD – SoD case is on hold because the SoD policy has been deactivated.
• CLOSED – SoD violation was closed, most likely because it no longer is a violation.
• HAS_ALL – Condition is violated if user or account has all of the permissions or technical roles specified in the
SoD condition.
• HAS_ANY – Condition is violated if user or account has any of the permissions or technical roles specified in the
SoD condition.
• HAS_MULTIPLE – Condition is violated if user or account has two or more of the permissions or technical roles
specified in the SoD condition.
• INACTIVE – The role or sod is not active and, no detections are performed.
Technical Reference 46
• INVALID – The role or sod is invalid and detection cannot be performed.
• ACTIVE – Valid, meaning all included permissions are available in the catalog, and the role is included in the
detection process.
• INACTIVE – Valid; however, the role is excluded from the detection process.
• INVALID – Invalid and excluded from detection process due to a detected error. Detection errors are usually the
result of a deleted permission that is included in the technical role.
• MINED -- Technical role was created by role mining and must be promoted before it can be activated.
• BUSINESS_ROLE_AUTO_GRANT – Technical role assign came from business role auto grant.
• BUSINESS_ROLE_AUTO_REVOKE – Technical role unassign came from business role auto revoke.
• AVE - The risk is calculated from the average of the risk all permissions included in the technical role
• MAX – The risk is set to the maximum risk of the permissions included in the technical role.
Technical Reference 47
Index of ENUMs
Technical Reference 48
ReviewPartialApprovalType ........................................ 39 SnapshotType ............................................................. 35
ReviewRepeatAfterType ............................................. 43 SodCaseActionType .................................................... 45
ReviewStartType ......................................................... 39 SodCaseState ............................................................. 45
ReviewStatus .............................................................. 40 SodConditionType ....................................................... 46
ReviewTargetDataType .............................................. 40 TechRoleAssignmentType .......................................... 47
ReviewTargetType ...................................................... 41 TemplateEventType .................................................... 21
ReviewTaskStatus ...................................................... 42 TemplateState ............................................................. 22
ReviewType .......................................................... 37, 41 TemplateType.............................................................. 22
RiskFactorOperation ................................................... 44 TimeUnitType .............................................................. 35
RiskFactorType ........................................................... 44 UnificationAnomaly ...................................................... 26
RiskMode .................................................................... 47 UnificationBehavior...................................................... 27
RiskScoreStatusType .................................................. 44 UserType ....................................................................... 9
SelfReviewPolicyType ................................................. 43 VerifyTaskState ........................................................... 36
SnapshotStatus ........................................................... 35
Technical Reference 49
Legal Notice
The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth
in the express warranty statements accompanying such products and services. Nothing herein should be construed as
constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained
herein. The information contained herein is subject to change without notice.
Technical Reference 50