Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

How to store the p12 file in SAVIYNT_HOME/Conf directory

Prashant16
New Contributor II
New Contributor II

Hi Team,

We have requirement to integrate the Google Apps with Saviynt and when we followed the connector guide it says to place the p12 file in SAVIYNT_HOME/Conf directory. Could you please provide the instructions to store this file so that we can test the connection.

However, we have gone through the entire connector guide but unable to find the steps to store this file in the respective directory.

Also as per the steps in guide, we have tried the service_account_key_json, but we are getting '400 Bad request error'. Below is the JSON format we have used in the connector.

{

  "type": "service_account",

  "project_id": "myorggapp-5XXXX6",

  "private_key_id": "aXXXXX733XXXXXXXbfc3224XXXXXX67a5",

  "private_key": "-----BEGIN PRIVATE KEY-----

  \nMIIEvgIBADANBgkqhkiG9w0BAQEFAASCBKgwggSkAgEAAoIBAQDWDHB+ZHRJlJsc

  \na6doaaBx+lX1Bm49cLqOxJXXXXXXXXXXXXXXXXXXXX/+xGRMxoGl7I3DwIbdkn7ydTvbR7mD0cHmA3TAgudmuJWkDp9XjOOKS9k/s0+C

  \nLAn8ttmoMMNwUyPnt/RIrrFMFy0LYHeSPhQfku1x61IZs8A1pbZEWdMOXRquxD48

  \nyJlb7YyVAgMBAAECggEAKOIQXHvIYENziM+4Vh220GDLJtlScKQKBgGdi9/KPsihtPi77Nfxe

  \ntNQBV2Z0hYyvt7vU2zP8L70v04JbtW7M1rQXgX/Iv/NLFPRUcq3AVwLvApDNvCH9

  \nOW6MA0rZXXXXXXXXXXXXXXXXXXXXXX4d0Sqh

  \n-----END PRIVATE KEY-----\n",

  "client_email": "XXXXX",

  "client_id": "XXXXXXXXX",

  "auth_uri": "XXXXX",

  "token_uri": "XXXXX",

  "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",

  "client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/usergcpandgapps%40myorggapp-5XXXX6.iam.gserviceacc..."

}

7 REPLIES 7

vivek9237
Regular Contributor
Regular Contributor

From Release v23.8, the REST connector uses the default path of key file that you upload under Admin > Settings > File Directory > Connector Files for creating a connection. Instead of the absolute path, specify the file name that contains the public-private keypair. For more information about uploading connector files, see Configuring File Directories in the Enterprise Identity Cloud Administration Guide.

 

Regards,

Vivek Mohanty


If this reply answered your question, please click the Accept As Solution button to help future users who may have a similar problem.

rushikeshvartak
All-Star
All-Star

Upload under connector files


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

Prashant16
New Contributor II
New Contributor II

Hi @vivek9237  and @rushikeshvartak ,

We have uploaded the file in saviynt by following the above guide but its giving file didn;t found error.
We are using below file path under the "CONNECTOR_FILE_PATH" attribute 

File path :"<SAVIYNT_HOME>/Conf//GoogleWorkspace.p12"
or "

https://removed.saviyntcloud.com/ECM/ecmConfig/fileDir/GoogleWorkspace.p12



if you have sample path can you please share it .

[This message has been edited by moderator to mask URL]

Specify below path

Path/saviynt_shared/saviynt/ConnectorFiles/GoogleWorkspace.p12

 

please remove domain name from previous post


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

Hi @Prashant16 try with the below file path

/saviynt_shared/saviynt/ConnectorFiles/GoogleWorkspace.p12

Regards,
Naveen Sakleshpur
If this reply answered your question, please click the Accept As Solution button to help future users who may have a similar problem.

Prashant16
New Contributor II
New Contributor II

Hi @naveenss @rushikeshvartak @vivek9237 ,
We have added the file path as mentioned but getting the below error, please let us know if you have any idea about this error. We have used the below configuration in connection.

Prashant16_0-1715322322542.png

Prashant16_1-1715322462373.png

 

 






Restart the application and try. if this does not work raise support ticket


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.