Issues with using the SAPgui connection component from the Marketplace.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Issues with using the SAPgui connection component from the Marketplace.

L2 Linker

I verified what I already have built into my 10.3 platform for SAPgui matches what is in the Market place. When attempting to launch the PSMSAPGUI.exe via the Dispatcher, I get the error below. 0682J000005OtXRQA0.jpg

if I try running the PSMSAPGUI.exe right from the PSM server, I get this:0682J000005OtY5QAK.jpg

Below is the component code in use:

<ConnectionComponent Id="PSM-SAPGUI" Type="CyberArk.PasswordVault.TransparentConnection.PSM.PSMConnectionComponent, CyberArk.PasswordVault.TransparentConnection.PSM"> <ComponentParameters /> <UserParameters> <Parameter Name="AllowMappingLocalDrives" Type="CyberArk.TransparentConnection.BooleanUserParameter, CyberArk.PasswordVault.TransparentConnection" Value="No" Visible="No" Required="Yes" /> </UserParameters> <TargetSettings Protocol="RDP" ClientApp="PSMSAPGUI.exe" ClientDispatcher="&quot;{PSMComponentsFolder}\PSMSAPGUI.exe&quot; &quot;{PSMComponentsFolder}&quot;" ClientInvokeType="Dispatcher" ConnectionComponentInitTimeout="35000"> <ClientSpecific> <Parameter Name="WaitBeforeCmdlineParmsHide" Value="2000" /> <Parameter Name="CmdLineParmsHideTimeout" Value="2000" /> <Parameter Name="Path" Value="C:\Program Files (x86)\SAP\FrontEnd\SAPgui\SAPgui.exe" /> </ClientSpecific> <LockAppWindow Enable="Yes" MainWindowTitle="SAP Easy Access" MainWindowClass="SAP_FRONTEND_SESSION" Timeout="2000" SearchWindowWaitTimeout="30" /> <Capabilities> <Capability Id="KeystrokesAudit" /> <Capability Id="KeystrokesTextRecorder" /> </Capabilities> </TargetSettings> </ConnectionComponent>

Below is a screenshot of the Client Dispatcher log:

0682J000005OtYeQAK.jpg

1 accepted solution

Accepted Solutions

The connection component is searching for a parameter, named SystemNumber, that should be set inside the account that you are using to connect, not in the connection component configuration. This Parameter should be present in the relevant platform

 

 

and should be set in your -SAP account:

 

 

Regards,

Roberto

View solution in original post

10 REPLIES 10

L2 Linker

You need to value the SystemNumber parameter in the account details, or add it to the platform if it is not present.

I'm not quite sure I follow. Below is what is set for the Connection Component. We have numerous SAP environments we are trying to use this to connect to also.

0682J000005Ov4gQAC.jpg

0682J000005Ov50QAC.jpg

The connection component is searching for a parameter, named SystemNumber, that should be set inside the account that you are using to connect, not in the connection component configuration. This Parameter should be present in the relevant platform

 

 

and should be set in your -SAP account:

 

 

Regards,

Roberto

L2 Linker

If you are attempting to use a Domain credential to connect to different endpoints, you can try to add a File Category to the Domain Account object. This can be added in the Platform under UI & Workflows -> Properties -> Optional

 

Name: SystemNumber

L2 Linker

Thank you both. I found the separate SAP platform that had the System Number parameter defined and I was able to get a successful connection working with our SAP team. The only issue I have now is that the command line passes a parameter 00 to the connection string and causes an error unless there is a user created in SAP with the 00 added. See below.

 

SAPgui.exe /SHORTCUT=" -system=DEV -client=020 -user=xxxx -pw="xxxx" -maxgui -guiparm="/R/DEV/M/xxx.xxx.com/G/CYBERARK 00""

 

0682J000005OwKzQAK.jpg

L2 Linker

@Robert Vipperman​ , A fix for this issue has been uploaded to the Marketplace.

L3 Networker

What does the "fix" do? Does it simply remove the trailing field (00) or specify a "correct" parameter placement in the field? One thing that is maddening here is the differences in terminology between vendor spaces.

It replaces it with the SystemNumber parameter from the account.

May we kindly ask how to allow custom command line parameter argument with the official Marketplace SAP PSM plugin?

Dear Rvipp,

 

How did you manage to make it work with the System Number?

I have the same issue and I can't connect, because the System Number needs a number as a value and does not accept a string like "DEV".

He accepts but then does not work properly.

I see that on the address you are using a specific syntax instead of the server ip or FQDN.

What should we put in fact on the Address field of the account?

 

Thank you,

Nelson

  • 1 accepted solution
  • 1548 Views
  • 10 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!