Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.
This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Issue configuring Windows Master PAM Connection

Go to solution
jdfranco
New Contributor III
New Contributor III

‎04/25/2023 11:56 AM - edited ‎04/25/2023 01:29 PM

Similar to the issues in this thread: https://forums.saviynt.com/t5/privileged-access-management/configuring-master-windows-pam-connection...

We are getting the following error when attempting to test the windows master connection in our new environment:
 
2023-04-24T17:42:25+05:30-arsms-2023-04-24T12:12:25.680141837Z stdout F 2023-04-24 12:12:25,680 [elastic-apm-server-reporter] WARN co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - It seems like you are using a version of the APM Server which is not compatible with this agent. Please use APM Server 6.5.0 or newer.
 
According to other posts here, it seems that this error can be ignored. 
 
Attached is the connection config as well as a more extensive log of the error.
 
We have also verified the prerequisites for the master connection are set up on the connection end.
Preview file
95 KB
Preview file
5 KB
0 Kudos
3 REPLIES 3

Go to solution
NageshK
Saviynt Employee
Saviynt Employee

‎04/27/2023 09:12 AM

@jdfranco Thanks for posting your question here. Yes, you can ignore those APM errors. From your screenshot I can see that the connection is not showing the windows verion which implies that the prerequisites are not complete. 

Please follow the steps mentioned in the section "Preparing EIC for Integration" in this article : 
https://docs.saviyntcloud.com/bundle/WindowsServer-v23x/page/Content/Understanding-the-Integration-B...  

Once these steps are complete, you should see the windows::1.0 in the dropdown as shown in the attached screenshot

Thanks

Nagesh K

Preview file
64 KB
0 Kudos

Go to solution
jdfranco
New Contributor III
New Contributor III
In response to NageshK

‎04/27/2023 12:09 PM

Thanks @NageshK , I have a ticket submitted for the last step of the EIC integration, Register the Windows Server JAR file.

We were told that SC2.0 can manage the endpoints on its own and we are not using the windows connector server. See the attached screenshot for the deployment we are trying to achieve. 

Preview file
189 KB
0 Kudos

Go to solution
NageshK
Saviynt Employee
Saviynt Employee

‎04/27/2023 01:54 PM

@jdfranco The jar file is what is referred to as the windows connector. It is more of a plug-in and not a server. Yes, SC 2.0 will facilitate the connections to the targets. The deployment model in the screenshot looks good. 

Thanks

Nagesh K

0 Kudos
Copyright © 2024 Khoros, LLC