- 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.
The following document describes how to integrate SIA with a Self-Hosted Vault-
Integrate with Secure Infrastructure Access
Under the following section 'Configure the PVWA to integrate with SIA' we are instructed to validate the end user's JWT token in Idira Identity for security best practices.
Below are the steps to find the exact information int he customer Identity ISPSS tenant so that they can be configured in PVWA.
Note 1- This feature is only supported in PVWA 14.4 and above.
Note 2- The PVWA requires connectivity to the internet. Alternatively, configure a proxy that allows it that connection. Proxy can be configured at the last step.
In PVWA go to:
Administration> Configuration Options > Options > ExternalServices > IdentitySIA.
Note- If ExternalServices does not exist, right-click Configurations and select Add ExternalServices.
Then right-click ExternalServices and select Add IdentitySIA.
Open the Identity tenant in a new tab or browser window.
In Identity go to:
Waffle Button > Identity Administration > Apps & Widgets > Web Apps
Select the built-in web app "Idira OIDC Trust App" and copy two values from the app configuration data-
Go back to PVWA and set the following:
| Parameter | Value |
| OptionalJWTValidation | Yes |
| IdentityAddress | The address copied from the Identity web-appv (example- https://abx1234.id.cyberark.cloud) |
| IdentityAppName | The App ID copied from the Identity web-app (example- __idaptive_cybr_user_oidc) |
If a proxy is used to connect the PVWA server to the internet, set the proxy configuration in the proxy parameters per the official document linked at the top of this article (UseProxy, ProxyHost, ProxyPort).
Apply and save the configuration.
Note- For testing phase only, you can set the parameter 'OptionalJWTVali)dation' to 'No' and JWT validation will be skipped.
To trouble shoot this feature, first enable trace level debug in PVWA, this level of debug is not enabled from the PVWA Web UI, but from adding a key in the PVWA web.config, default path "C:\inetpub\wwwroot\PasswordVault\web.config"
Edit the file and find the end of the AppSettings tag i.e. </appSettings> and add the following line above it:
<add key="FullDebugMode" value="yes" />
The save the file and perform an IISRESET from an administrator command prompt window.
Example of web.config:
Note- If testing against a load balanced environment, this must be done on all PVWA's in the pool that the session might go to.
After adding this debug level, and repeating the test session, we will see a new file in the PVWA logs folder (Default path: C:\Windows\Temp\PVWA) labeled "CyberArk.FullDebug.log"
Open this file and search for lines regarding JWT Token Validation.
For example the request below failed due to an incorrect application address (tenant address was entered instead of application URL):
---
| PASWS001E Error occurred: Failed to send the request
| CyberArk.PasswordVault.WebServices.Infra.Exceptions.SiaRequestException: Failed to send the request ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond x.x.x.x:443
.
.
.
at CyberArk.PasswordVault.WebServices.Infra.Filters.CloudServicesAuthorizationAttribute.ValidateJwtToken(HttpClient client, String url, Dictionary`2 requestContent)
---
Reminder: When troubleshooting is complete, do not forget to remove the debug level key from web.config and perform another IISRESET.