Chat now with support
Chat with Support

We are currently experiencing issues on our phone support and are working diligently to restore services. For support, please sign in and create a case or email supportadmin@quest.com for assistance

Identity Manager On Demand Hosted - IT Shop Administration Guide

Setting up an IT Shop solution
One Identity Manager users in the IT Shop Implementing the IT Shop Using the IT Shop with the Application Governance Module Requestable products Preparing products for requesting Assigning and removing products Preparing the IT Shop for multi-factor authentication Assignment requests Delegations Creating IT Shop requests from existing user accounts, assignments, and role memberships Adding system entitlements automatically to the IT Shop Deleting unused application roles for product owners
Approval processes for IT Shop requests
Approval policies for requests Approval workflows for requests Determining the effective approval policies Selecting responsible approvers Request risk analysis Testing requests for rule compliance Approving requests from an approver Automatically approving requests Approval by peer group analysis Gathering further information about a request Appointing other approvers Escalating an approval step Approvers cannot be established Automatic approval on timeout Halting a request on timeout Approval by the chief approval team Approving requests with terms of use Using default approval processes
Request sequence Managing an IT Shop
IT Shop base data Setting up IT Shop structures Setting up a customer node Deleting IT Shop structures Templates for automatically filling the IT Shop Custom mail templates for notifications Request templates Recommendations and tips for transporting IT Shop components with the Database Transporter
Troubleshooting errors in the IT Shop Configuration parameters for the IT Shop Request statuses Examples of request results

Troubleshooting errors in the IT Shop

Timeout on saving requests

If new requests are saved in bulk in the database a timeout may occur, after importing data, for example.

Probable reason

By default, the approvers responsible are determined during saving. This delays the saving process. No more actions can take place in One Identity Manager until all requests are saved and, therefore, all approvers have been found. Depending on the system configuration, this may cause a timeout to occur when large amounts of data are being processed.

Solution
  • In the Designer, disable the QER | ITShop | DecisionOnInsert configuration parameter.

Effect
  • The requests are saved and a calculation task for determining approvers is queued in the DBQueue. Approvers responsible are determined outside the save process.

  • If the requester is also the approver, the approval step is not automatically granted approval. Approvers must explicitly approve their own requests. For more information, see Automatically approving requests.

  • Automatic approval decisions are also met if necessary, but are delayed. This affects requests with self-service, for example.

Bulk delegation errors

You have the option to delegate all your responsibilities to one person in the Web Portal. If you have a lot of responsibilities, it is possible that not all the delegations are carried out. A delegator can send a notification to themselves if an error occurs.

Probable reason

An error occurred processing delegations. VI_ITShop_Person Mass Delegate was stopped, although only a fraction of the delegations has been applied.

Solution
  1. Configure the notification procedure.

  2. Run all remaining delegations again in the Web Portal.

Related topics

Process monitoring for requests

For more information about process monitoring in One Identity Manager, see the One Identity Manager Configuration Guide.

To configure process monitoring for requests

  1. In the Designer, check whether the Common | ProcessState configuration parameter is set. If not, set the configuration parameter.

    If this configuration parameter is set, a process monitoring entry (DialogProcess table) is created when the request is created.

  2. In the Designer, check the Common | ProcessState | UseGenProcIDFromPWO configuration parameter.

    If this configuration parameter is set, the GenProcID of an IT Shop request is retained for the entirety of the approval process.

    If the configuration parameter is not set, a new GenProcID is used for each approval decision.

  3. In the Designer, check the QER | ITShop | GenProcIDBehavior configuration parameter

    Set the configuration parameter and use the value to specify how many GenProcIDs should be generated for a shopping cart's requests.

    • MultiID: Generates a new GenProcID for each shopping cart request.
    • SingleID: Generates one GenProcID for the entire shopping cart. All requests created through the shopping cart are given the same GenProcID.

    If the configuration parameter is not set, a separate GenProcID is generated for each shopping cart request.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating