Can someone explain the web form fields in a Web App XML file?

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

Can someone explain the web form fields in a Web App XML file?

L0 Member

I tried making a Web Connector with the PGU, however I believe something about the site is incompatible with the PGU, so the connector isn't generated properly. I was thinking I could edit the generated XML file to have the proper webform fields to try to get it working.

 

However, I'm a little confused by what the fields mean. For Example:

email>{Username}(SearchBy=id)


 

When the connector reads this, what happens? Is it searching for an email element by id, and then stating the value as variable {username}?

What if I wanted to hardcode a value like username into the web form fields, would I still use brackets or could I just enter the value after the semicolon:

email>TestEmail(SearchBy=id)

 

Any help or pointing in the right direction would be great. I've been having trouble figuring this out through the documentation.

3 REPLIES 3

Hi @Tanner Herring​ 

 

Can you consult this documentation https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasimp/psm_webapplication.htm#configureCPMPSM this explain the webform fields and the structure of connection components for webapps.

 

Regards

 

Patricio Henriquez Estay

L3 Networker

The format is kind of wonky for a human to process.

The first element in the line is the element you're seeking on the HTML page.

The second element in the line is the account attribute or text you wish to put in to the field OR the action you want to take (click button).

The final element in the line is a clarification on how to search the HTML page for the element.

 

Your example email>{Username}(SearchBy=id)
 looks broken to me. There shouldn't be anything after (SearchBy=ID) and the > should actually just be the greater than > symbol.

 

Here's an example from one of my platforms

j_username>{username}(SearchBy=id)

j_password>{password}(SearchBy=id)

logOnFormSubmit>(Button)(SearchBy=id)

 

This can be read as:

Find the HTML element 'j_username' by it's ID in the page. Put the account's username into that field.

Find the HTML element 'j_password' by its ID in the page. Put the account's password into that field.

Find the HTML element 'logOnFormSubmit' by its ID in the page. Click that button.

 

My team builds these from scratch with far more reliability than using PGU. In fact, I've never had PGU succeed in a real-world application rather than a lab, but that's probably just my sample set of apps that I've worked with...

PGU also doesn't handle CPM activities. Manual construction of webformfields code can via ini files on your CPM server.

L4 Transporter

Hi @Tanner Herring​ 

 

Since several community members answered your question, could you kindly share if any of these solutions resolved your issue?

If so, could you please mark the appropriate answer as "Select as Best" to assist other community members.

 

If the issue is still relevant, I would advise raising a ticket with our Support team for further assistance.

 

Thank you,

Liad

  • 608 Views
  • 3 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!