PhenixID

PSD1101 – ARS-Remedy Actions for Identity Provisioning

Fact

  • PhenixID Identity Provisioning 5.1 or later

System Requirements

  • ARS-Remedy REST endpoint url for authorization and access management service request, web service username and password. (Must be setup by the ARS-Remedy admin)

Situation

Use PhenixID Identity Provisioning to create BMC Remedy access management service requests, used to delegate cost approval to another user.

Solution

This document will show the steps that are necessary to configure PhenixID Identity Provisioning to create BMC Remedy service request.

Download and install the action package

Download the zip file:

ArsRemedyActionPackage.zip

For instruction of how to install the action package, read PSD1149.

Actions

Create BMS ARS/Remedy Access Mgnment Service request

This action creates a ARS-Remedy Access Mgnment service request.

NB! For a detailed flow- and api specification for the ARS-Remedy web service, please contact your ARS-Remedy administrator.

Parameter

Description

Example

Authorization web service URL

[MANDATORY] BMS ARS-Remedy REST endpoint URL to obtain JWT token. The JWT token will be passed in subsequent calls to BMS Remedy Service Request endpoint.

 http://demo6962066.mockable.io/jwttoken

WS Username

[MANDATORY] BMS ARS-Remedy REST username

user1

WS Password

[MANDATORY] BMS ARS-Remedy REST password

secret

Create BMS Remedy Service request Web Service URL

[MANDATORY] REST endpoint for creating the service request.

 http://demo6962066.mockable.io/remedy/create

Session attribute for Approver A User Login ID

[MANDATORY] The session attribute that contains Approver A User Login ID. Users with this role will submit a new request for an alternate approver in the external system Attest & Delegation.
He/she will be the approver of the created Service Request in Remedy.

The session attribute value will be used to populate the RequestedByLoginID json property of the request payload.

approvera

Session attribute for Approver B User Login ID

[OPTIONAL] The name of the session attribute that contains Approver B User Login ID. This is the user to whom the alternate approvers permissions are given.

The session attribute value will be used to populate the RequestedForLoginID json property of the request payload.

 approverb

Session attribute for Cost Center Code

[MANDATORY] The name of the session attribute that contains the cost center code.

The session attribute value will be used to populate the Q3 Value_char_255 json property of the request payload. The json property Q3 Label will always be set to “Cost Center Code”.

costcenter

Session attribute for Start date

 [MANDATORY] The name of the session attribute that contains the start date. ((value must be in format yyyy-mm-dd.)

The session attribute value will be used to populate the Q11 Date  json property of the request payload. The json property Q11 Label will always be set to “Start Date”.

  startdate

Session attribute for End date

 [MANDATORY] The name of the session attribute that contains the end date. ((value must be in format yyyy-mm-dd.)

The session attribute value will be used to populate the Q12 Date  json property of the request payload. The json property Q12 Label will always be set to “End Date”.

 enddate

Session attribute for Approval Type

 [MANDATORY] The name of the session attribute that contains the Approval Type specific text.

The session attribute value will be used to populate the Q9 Value_char_0 json property of the request payload. The json property Q9 Label will always be set to “Approval Type Specific Text”.

 approvaltype

 Q1 Label

 [OPTIONAL] The value of Q1 Label. Any additional questions and their labels & answers that are present in the A&D System will be transferred via the interface and created in the Service Request in order to be visible in the MyIT system.

The value will be used to populate the Q1 Label json property of the request payload.

 q1label

Session attribute for Q1 Value

 [OPTIONAL] The name of the session attribute that contains Q1 Value. Any additional questions and their labels & answers that are present in the A&D System will be transferred via the interface and created in the Service Request in order to be visible in the MyIT system.

The session attribute value will be used to populate the Q1 Value_char_255 json property of the request payload.

 q1value

Q2 Label

 [OPTIONAL] The value of Q2 Label. Any additional questions and their labels & answers that are present in the A&D System will be transferred via the interface and created in the Service Request in order to be visible in the MyIT system.

The value will be used to populate the Q2 Label json property of the request payload.

 q2label

Session attribute for Q2 Value

 [OPTIONAL] The name of the session attribute that contains Q2 Value. Any additional questions and their labels & answers that are present in the A&D System will be transferred via the interface and created in the Service Request in order to be visible in the MyIT system.

The session attribute value will be used to populate the Q2 Value_char_255 json property of the request payload.

 q2value

Session attribute to populate with error

 [OPTIONAL] In case of an error, this session attribute will be populated after execution. Defaults to “errorMessage”. error_mess

Q3 Label

 [OPTIONAL] The Q3 Label value. Will be used to populate the Q3 Label json property of the request payload.

Q9 Label

 [OPTIONAL] The Q3 Label value. Will be used to populate the Q9 Label json property of the request payload.

Q11 Label

 [OPTIONAL] The Q3 Label value. Will be used to populate the Q11 Label json property of the request payload.

Q12 Label

 [OPTIONAL] The Q3 Label value. Will be used to populate the Q12 Label json property of the request payload.

Example usage

Execution
  1. Action config
  2. Policy in runtime. Session object before executing the ARS-Remedy action.

    The data in the picture above will be used to construct the json payload of the request to the ARS-Remedy Service Request endpoint. Above example will generate this json payload:

     {
 "values":{
 "Q3 Label":"Cost Center Code",
 "ServiceRequestDefinitionName":"Access Management SRD",
 "Q3 Value_char_255":"CostcenterCCC",
 "Q9 Label":"Approval Type Specific Text",
 "Q2 Value_char_255":"Q2 value.",
 "Q11 Label":"Start Date",
 "Q1 Label":"My Q1 label here",
 "RequestedForLoginID":"PekkaApproverB",
 "Q1 Value_char_255":"Q1 value",
 "Q12 Date":"2018-12-24",
 "Q9 Value_char_0":"Approval text here",
 "RequestedByLoginID":"AndersApprover1",
 "Q12 Label":"End Date",
 "Q2 Label":"My q2 label here",
 "Q11 Date":"2018-07-08"
 }
}
  3. Policy in runtime. Session object after executing the ARS-Remedy action. In this example, no error message attribute was added which means the execution was successful.
DISCLAIMER
Information provided in this document is for your information only. PhenixID makes no explicit or implied claims to the validity of this information. Any trademarks referenced in this document are the property of their respective owners.

The origin of this information may be internal or external to PhenixID. PhenixID makes all reasonable efforts to verify this information.

PhenixID - support.phenixid.se