Akamai Identity Cloud RCS Connector for synchronization between Akamai Identity Cloud and PingIDM / PingOne AIC.
Connector Features:
- Bidirectional synchronization (Akamai Identity Cloud ↔ PingOne IDM)
- Password migration
- Full support for custom attributes
Note: Custom attributes must be defined in both Akamai Identity Cloud and the PingOne IDM Native Console to be mapped and synchronized successfully.
Install and setup the Java RCS: https://backstage.forgerock.com/docs/openicf/latest/connector-reference/java-server.html
Once Java RCS openicf is downloaded, create a tools directory in the openicf directory. Place these groovy scripts in this tools directory.
There are also 3 libraries that need to be installed. These are called secrets-api, chf-http-core, and json-web-token. These can be installed in the /lib/framework directory of openicf. These jar files can be found by installing the latest of openidm, and finding those dependencies in the openidm/bundle folder. OpenIDM installation can be found here: https://backstage.forgerock.com/downloads/browse/idm/featured
For on-premises installations, follow these steps here: https://docs.pingidentity.com/pingidm/7.2/connector-reference/configure-connector.html#connector-wiz-REST.
Using the Platform UI, go to applications and browse app catalog. Select the Scripted Rest Connector.
After creating the connector, set these configurations:
| Property | Usage |
|---|---|
| Service Address | ${Akamai Tenant URL} |
| Proxy Address | |
| Username | ${Basic Auth Username} |
| Password | ${Basic Auth password} |
| Default Content Type | |
| Default Request Headers | |
| Default Authentication Method | BASIC |
| Custom Sensitive Configuration | |
| Script Roots | tools/ |
| Authenticate Script | |
| Create Script | CreateScript.groovy |
| Update Script | UpdateScript.groovy |
| Delete Script | DeleteScript.groovy |
| Search Script | SearchScript.groovy |
| Test Script | |
| Sync Script | |
| Schema Script | SchemaScript.groovy |
| Resolve Username Script Script | |
| Script On Resource Script | |
| Customizer Script | CustomizerScript.groovy |
Akamai Identity Cloud → PingIDM:
- In the Native Console, go to Identity Management > Configure > Mappings.
- Create a new mapping.
- Set the Akamai Scripted REST Connector as the source and the desired PingIDM managed object as the target.
PingIDM → Akamai Identity Cloud:
- In the Native Console, go to Identity Management > Configure > Mappings.
- Create a new mapping.
- Set the desired PingIDM managed object as the source and the Akamai Scripted REST Connector as the target.
After creating the mapping in either direction, you can configure property mappings to define which attributes synchronize between Akamai and PingIDM.
Example property mapping configuration:
The Akamai connector supports all standard Akamai Identity Cloud attributes as well as custom attributes defined in your Akamai schema.
- To synchronize custom attributes from Akamai Identity Cloud into PingIDM, you must first define the corresponding custom attributes in IDM.
Note: It is recommended that all schema attribute policies are turned off in order to avoid attribute mapping complications.
If you encounter any issues, be sure to check our Troubleshooting pages.
Support tickets can be raised whenever you need our assistance; here are some examples of when it is appropriate to open a ticket (but not limited to):
- Suspected bugs or problems with Ping Identity software.
- Requests for assistance
You can raise a ticket using BackStage, our customer support portal that provides one stop access to Ping Identity services.
BackStage shows all currently open support tickets and allows you to raise a new one by clicking New Ticket.
This Ping Identity project does not accept third-party code submissions.
This code is provided by Ping Identity on an “as is” basis, without warranty of any kind, to the fullest extent permitted by law. Ping Identity does not represent or warrant or make any guarantee regarding the use of this code or the accuracy, timeliness or completeness of any data or information relating to this code, and Ping Identity hereby disclaims all warranties whether express, or implied or statutory, including without limitation the implied warranties of merchantability, fitness for a particular purpose, and any warranty of non-infringement. Ping Identity shall not have any liability arising out of or related to any use, implementation or configuration of this code, including but not limited to use for any commercial purpose. Any action or suit relating to the use of the code may be brought only in the courts of a jurisdiction wherein Ping Identity resides or in which Ping Identity conducts its primary business, and under the laws of that jurisdiction excluding its conflict-of-law provisions.
This project is licensed under the MIT License - see the LICENSE file for details
© Copyright 2024 Ping Identity. All Rights Reserved