CPAM SC2.0 connection errors deploying into a Linux Master account

[alexb]

Problem: not able to connect with SC2.0 in our CPAM instance

-----------------

What we did:

-----------------

1. We have followed all the proceedures shown in the page:

https://docs.saviyntcloud.com/bundle/Saviynt-Connect-20-Resources/page/Content/Saviynt-Connect-20-Cl...

2. We have also checked all references to SC2.0 in the forums pages and Q&A of SC2.0

3. We tried all 3 scripts from the SC2.0 download file: sc2-package-install.sh, install_monitoring.sh, sc2-config-update.sh but they presented some errors related to packages not being found.

4. We checked the content of the .sh files and started to install packages manually and run all commands as described but could not get a connection.

--------------------- LOG -----------------------

-- Unit openvpn-client@52.XXXXX.70.service has begun starting up.

May 22 06:13:19 ip-10-XX-XX-58.di-aws-cpam.XXXX.fi openvpn[1594]: Options error: In [CMD-LINE]:1: Error opening configuration file: 52.XXXXXXX70.conf

May 22 06:13:19 ip-XXXXXXX.di-aws-cpam.XXXX.fi openvpn[1594]: Use --help for more information.

May 22 06:13:19 ip-XXXXXX.di-aws-cpam.XXXX.fi systemd[1]: openvpn-client@52.XXXXX.70.service: Main process exited, code=exited, status=1/FAILURE

May 22 06:13:19 ip-10-XXXXXX.di-aws-cpam.XXX.fi systemd[1]: openvpn-client@52.XXXXX.70.service: Failed with result 'exit-code'.

-- Subject: Unit failed

-- Defined-By: systemd

-- Unit openvpn-client@52.XXXX.70.service has failed.

-- The result is failed.

--------------------------------------------

Q. What could have been the cause of this error?

We would like to know in the configuration of the VPN, should we use public IP, Local IP also for the Saviynt IP, we have a few of them, which should be used for the configuration?

Saviynt INFO provided:

UI server ip's

------------------

Batch server ip

10.XXXXX.68

10.XXXXX.252

------------------

No changes in IP

10.XXXXX.42

-----------------

Public

IP: 52.XXXXX.70

-----------------------

Any thoughts?

[NageshK]

@alexb This is related to SC 2.0 setup. You should open an FD ticket for this and support team will create an internal ticket for the Infra team. Have you opened one already?

Thanks

Nagesh K

[alexb]

Thank you for the reply. 

Yes probably just configuration, but once again every connection should use the same procedure as far as I understood, so the settings to connect in a AWS environment is with company internal ip or public and from saviynt side their public or internal?  

The documentation doesn't specify which option should be used.

[NageshK · Accepted solution]

@alexb As discussed in the SME call, this has to go to FD. And please share the FD ticket here for reference. 

Thanks,

Nagesh K