RapidIdentity Product Guide: New UI

Alternate Edit Action

This alternate action is used to bypass built-in RapidIdentity Portal logic and instead allow an arbitrary RapidIdentity Connect Action Set to provide Edit Sponsored Account functionality. RapidIdentity Portal performs the necessary authentication/authorization/validation on the request then invokes the pre-defined Action Set on the configured RapidIdentity Connect instance. Note that when this Action Set is run that only the changed attributes will be sent.

Action Set Parameters
Table 331. Parameters

Parameter

Description

target_dn

The DN of the target of the operation (whose account is being updated)

perp_dn

The DN of the perpetrator of the operation (who's performing the operation)

audit_event_id

An audit event ID which may be used to correlate any audit log events from invoked Action Set to the audit log event generated by the call to the RapidIdentity Portal API

record_string

A JSON object containing the LDAP attributes defined in the Delegation and their new value(s). If all values for a particular attribute are being removed, then the value associated with the attribute will be null. See examples below.



Example

The following example shows a record_string value indicating that the target's LDAP entry should have an employeeType value of Sponsored, a givenName value of FirstName, a sn value of LastName, a multiValuedAttribute attribute with two values: value1 and value2, and no values for attribute deletedAttribute.

{"employeeType": "Sponsored", "givenName": "FirstName", "sn": "Last Name", "multiValuedAttribute": ["value1", "value2"], "deletedAttribute": null}

Action Set Return Value

{ "success": <boolean>, "message": <string>, "new_dn": <string> }

Table 332. Return Fields

Field

Description

Required

success

Whether RapidIdentity Portal should consider the action as successful

no, defaults to false

message

Optional message which will be passed through to the API response and ultimately to the UI.

no

new_dn

In the event that the profile update results in the target object being moved in the directory, this value should be populated with the target's new DN.

no



Example

{"success": false, "message": "The operation failed because...."}

{"success": true, "message": "The operation was successful", "new_dn": "cn=targetDN,ou=newOU,dc=example,dc=com"}