Enterprises using the TCPWave IPAM 11.22 P1 (Santa Lola) can leverage the seamless integration into the ServiceNow workflows. Activities such as Change Request Approval or Reporting an Incident or Planning a corrective plan of action that are performed in ServiceNow can be chained into the TCPWave Script Include Functions to invoke an appropriate API in a secure authenticated manner.
The architectural diagram above illustrates how user actions in ServiceNow can be chained to invoke outbound HTTP Rest Calls to TCPWave IPAM. The ServiceNow instance and TCPWave IPAM communicate using HTTPS (HTTP with SSL) to enforce industry standard security for mission critical operations. Here is an example of a workflow. When a change request to define a new static object is approved by a privileged user.
The example below illustrates the functionality using self-signed SSL certificates. However, TCPWave highly recommends the usage of valid certificates signed by trusted authorities for security reasons.
1. Create a Basic Java Keystore: keytool -genkey -alias <alias_name > -keyalg RSA -validity 365 -keystore servicenow.jks -storepass <your_password> -keypass <your_password>
The above figure illustrates importing servicenow.jks as a Java KeyStore in ServiceNow UI.
2. Export the certificate in servicenow.jks as servicenow.cer: keytool -export -alias <alias_name> -keystore servicenow.jks -storepass <your_password> -file servicenow.cer
3. Import servicenow.cer into TCPWave IPAM.
The above figure illustrates importing servicenow.cer as an appliance certificate into TCPWave IPAM. Please ensure that Trust CA is selected in the above screen during the Import.
The above figure illustrates importing servicenow.cer as a user certificate into TCPWave IPAM. This step is required to associate all the incoming HTTP Requests using this certificate to a user in the IPAM.
4. Import TCPWave SSL Certificate in ServiceNow.
The above figure illustrates importing TCPWave SSL Certificate into the ServiceNow Instance. This certificate is in the default DER Format.
5. Define Mutual Authentication Protocol in ServiceNow
The above figure illustrates defining a unique protocol and a key store to a default port.
Define Script Include Functions to invoke the TCPWave API
As illustrated in the figures above, a simple workflow called TCPWave_Integration has been defined to operate on the Change_Request Table. This workflow runs on two definitive conditions where the short_description is add_domain and the state of the Change Request is approved.
The Run Script definition presented in the figure shown above is going to derive the description and short_description fields of the current change request item and invoke the corresponding Script Include function.
The screenshot above is going to illustrate how a new change request is defined in ServiceNow by attaching short_description and description field with the appropriate values required for the TCPWave Integration.
Once the authorized administrator approves the Change Request - The workflow kicks in to complete the automation request - the above figure illustrates a successful execution of the workflow.
Because of a successful workflow execution, the screenshot above shows that a static object of type AWS Instance with the name AWS00001Instance.aaa.com has been added to the TCPWave IPAM.
The Webservices offered by TCPWave DDI can be extensively leveraged from applications such as ServiceNow to combine and automate Change Request Management and day to day DDI workflows without compromising security. The SSL Based authentication between ServiceNow and TCPWave IPAM enforces encrypted data exchange thus ensuring a trusted conduit. Enterprises using TCPWave DDI can now seamlessly integrate with ServiceNow and engineer custom workflows with endless possibilities to accomplish 100% safe and secure DDI Workflow Automation.