- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
01-23-2026 02:29 PM
Hello,
I am looking to setup okta sso psm via a web connector. I downloaded the connection component from here - https://community.cyberark.com/marketplace/s/#a3550000000El8TAAS-a3950000000jju2AAA
The goal is to enable IT team members to log in to Okta using a shared Okta admin account in order to perform privileged actions
However the webform fields in the connection component are outdated. I tried updating to this below
Updated:
input28>{Username} (searchby=id)
input36>{Password} (searchby=id)
Sign in>(Button) (SearchBy=Type)
Default:
okta-signin-username>{Username} searchby=id)
okta-signin-password>{Password}(searchby=id)
okta-signin-submit>(Button)(searchby=id)
(iframe)
row-label>(Button)(searchby=class)
Element:
<input type="text" placeholder="" name="identifier" id="input28" value="" aria-label="" autocomplete="username">
xpath:
//*[@id="input28"]
It is throwing me an error on line 1. I am not sure what is missing here. I copied element from browser. I also tried xpath adn still giving an error. Has anyone else setup okta sso psm connector? Any help will be appreciated!
01-26-2026 08:46 AM
Okta’s authentication platform contains multiple elements whose attributes can vary dynamically.
Because of this, the elements you want to input to or select must be uniquely identified using XPath with AND conditions. Fortunately, XPath allows the use of AND operators, enabling you to uniquely specify an element with conditions such as:
contains(@id, "input2") and contains(@id, "XXXXX")By providing the full XPath related to the login sequence to a generative AI tool and asking it to produce a uniquely identifiable XPath, you should be able to implement a reliable solution.
01-25-2026 07:19 PM
I'm not sure if web form field can contain space, "Sign in>(Button) (SearchBy=Type)".
01-25-2026 08:36 PM
I'm not certain whether this matches your environment, but the element structure of a certain web application that uses Okta as its authentication platform was similar. Trying the following approach may help resolve the issue:
//*^[contains(@id, "input2")^] > {Username} (SearchBy=XPath)The reason I described it this way is that the “8” in input28 can vary depending on the access timing.
01-26-2026 08:08 AM
Looks like im no longer getting an error on line 1. Instead im getting on line 3. Error is unable to parse line 3
input28 > {Username} (searchby=id)
input36 > {Password} (searchby=id)
//*^[@id="form20"^]/div^[2^]/input > {Button} (SearchBy=XPath)
Element:
<input class="button button-primary" type="submit" value="Sign in" data-type="save">
I am not sure what is missing.
01-26-2026 08:46 AM
Okta’s authentication platform contains multiple elements whose attributes can vary dynamically.
Because of this, the elements you want to input to or select must be uniquely identified using XPath with AND conditions. Fortunately, XPath allows the use of AND operators, enabling you to uniquely specify an element with conditions such as:
contains(@id, "input2") and contains(@id, "XXXXX")By providing the full XPath related to the login sequence to a generative AI tool and asking it to produce a uniquely identifiable XPath, you should be able to implement a reliable solution.
01-26-2026 11:49 AM
Thank you, Lori. I tried using fullpath and I am not getting that error anymore but getting validation verification errors now. Do I need to have the validation verification row as well?
01-26-2026 03:41 PM
Regarding validation, it is also possible to turn it off.
In my environment, I set the following option to No so that validation does not run:
<connection component> → Target Settings → Client Specific → Run Validations
If you want to improve the reliability of logins, I think it is preferable to enable it, but at least in my environment I have not encountered any issues.
01-26-2026 03:58 PM
The parameters for the Connection Component are described in the “Run Validations” section of the following URL:
https://docs.cyberark.com/pam-self-hosted/latest/en/content/messages/web%20applications%20messages.htm
01-27-2026 06:47 AM
This removed the error and is now working!
This was my final
input28 > {Username} (searchby=id)
input36 > {Password} (searchby=id)
/html/body/div^[2^]/div^[2^]/main/div^[2^]/div/div/div^[2^]/form/div^[2^]/input > (Button) (SearchBy=XPath)
01-27-2026 06:58 AM
Hi Lori,
Quick question, if I needed to rotate password for okta admin users using this setup, can you direct me to the documentation for that?
01-27-2026 05:51 PM
I'm glad to hear that everything worked out well.
Please take a look at this.
One thing to note is that, unlike PSM connections, password changes require a final Validation step.
https://docs.cyberark.com/pam-self-hosted/latest/en/content/plugins/cpm_webapplication.htm
If you have identified the URL of the password‑change page, you can use the following to navigate to that page:
(Navigate=URL)
From there, you should be able to perform the password change just as you do during login, and then complete the process with Validation.
01-28-2026 06:34 AM
Thank you, lori. I ran into an issue after logging in via the okta sso psm web connector. Few minutes after logging in and verifying with okta verify, the cyberark session kicks me out. Even though validation is turned off, it is still looking for validation? is this expected?
01-28-2026 02:21 PM
Hi Salam,
Based on the message, it seems that the validation parameters may not actually be disabled.
In my case, I customized the PSM-WebAppSample and simply set the value of RunValidations to "No", and it has been working stably for about a year without any issues.
You should be able to find in the logs below where the validation is being executed and where it fails:
PSM Installation Folder\Logs\Components\
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!

