SecZetta Integration WebService connector Authentication

[YIOA1 (Yamini O)]

Hi,

Has anyone configured SecZetta as a WebService (REST API) source in IDN? Using token to connect with SecZetta, even if I mention it in source connection settings I need to give token details in header of operations for account aggregation . Authorization :Token token=xxx . Want to avoid this and pass it as encrypted value? if I mention Authorization_CA will it make secure? I also did try creating one more operation custom authentication and using authenticity_token (getting access denied in postman as well)

[iam_nithesh (Nithesh Rao)]

Check if this post helps you

How to use more than one endpoint in a WS connector?

We had a similar case where we had to get an auth token from one end point and add it to the header of the API request being sent for any of the operations As this was not happening with the standard configuration settings available in IDN, this is what we did: Set up only one Http Operation with second Endpoint in the context URL Call the first End Point to get “someID” (using org.apache.http.impl.client.HttpClientBuilder or sailpoint.connector.webservices.WebServicesClient) from inside the …

[Kurt_Ramsey]

Warning
When configuring the source, do not hard code sensitive data. If sensitive data is hard coded, it can lead to that data being exposed when moving to a production environment. SailPoint recommends putting sensitive information in the encrypted attribute value list in the application XML and then using the encrypted variable name when configuring the source. For example, if you want to add the custom variable Custom_Variable in the encrypted list, append the variable name in the following list: <entry key="encrypted" value="accesstoken, refresh_token, Custom_Variable"/>

https://documentation.sailpoint.com/connectors/webservices/help/integrating_webservices/introduction.html

To add the custom variable and update the values in encrypted, you will need to update the source via API.

[Kurt_Ramsey]

Though in the case of SecZetta/NERM, you should be able to the “API Token” authentication type

[YIOA1 (Yamini O)]

@iam_nithesh . @Kurt_Ramsey Thank you for responding. yes was able to do passing hardcoded token through UI but want to avoid. This is fixed now. Passing in before rule “access token” value the authorization value instead of UI and retrieving it in operations.

[YIOA1 (Yamini O)]

If we set the api token in connector settings of source in UI we again need to pass hardcoded token in operations and unable to retrieve using “$application.accesstoken$” so did set this using before rule.