SAML ITATS894E An unhandled exception has occurred

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

SAML ITATS894E An unhandled exception has occurred

L1 Bithead

Hi,

This is weird. I've recently deployed Remote Access using SAML Auth on Self-Hosted 12.6. It was working fine, creating new users in the Vault as expected via VendorLDAP.

 

During testing in the last few days, only old existing Vendor accounts were working, and any new Vendor account we created started getting errors:

 

PVWA.App.Log reflects this.

2024-09-27 16:05:37,395 || ERROR  || 77 || || || f05e8d0f-e3fb-4831-8e9a-8cce41c72258 || ITATS894E An unhandled exception has occurred. (Vault [CAMainVault] user [Christopher.Pols-Vendor.J-Group-Consulting.alero]) || || Casos

2024-09-27 16:05:37,395 || ERROR  || 77 || || || f05e8d0f-e3fb-4831-8e9a-8cce41c72258 || ITATS894E An unhandled exception has occurred. (Vault [CAMainVault] user [Christopher.Pols-Vendor.J-Group-Consulting.alero]) || || Casos

2024-09-27 16:05:37,395 || DEBUG  || 77 || || || f05e8d0f-e3fb-4831-8e9a-8cce41c72258 || CASW084D Error in DoLogonAs. Error [ITATS894E An unhandled exception has occurred.

 

There have been no changes as far as I know, we've rechecked VendorLDAP, that looks fine. Anything that would make sense as to why this would be working, and then suddenly not? I've restarted the PVWAs, Remote Access connector servers etc.

The Vault italog has nothing that explains it.

 

Any ideas where I need to look?

Field_Content_versions_oct20__068Ht00000VerYrIAJ.png

2 REPLIES 2

L7 Applicator

Hi @Chris Pols​ 

 

There are few areas to check here,

 

  • There might be an issue with how the new vendor accounts are being created in the Vault through VendorLDAP. Even though VendorLDAP is configured correctly, there could be a sync issue that prevents new users from being fully provisioned in the Vault.
  • Please review the LDAP sync logs to see if new users are being successfully added or if there are any errors.
  • Please test manual authentication using new vendor accounts to ensure the authentication is still working for new accounts.
  • Also please validate that the SAML attributes are correctly mapped to the new vendor users in VendorLDAP
  • In addition, please verify that the SAML assertion for new users includes all required attributes (e.g., UPN, Email, Roles, etc.) that map to Vault user properties. Any missing attributes could cause the authentication to fail.
  • You can compare the SAML response for an old working vendor account and a new failing one to spot any discrepancies.
  • Please verify if there’s a permissions issue specifically with new vendor users being added to the Vault

 

I would try a workaround by manually adding a new vendor user directly in the Vault and test authentication to isolate whether it’s a user provisioning or authentication issue.

 

Hope it helps !

L1 Bithead

Hi @Malhar Vora​ 

 

So after a bunch of troubleshooting VendorLDAP, our RPAM connector servers etc, we found that the main LDAP directory connected started having auth issues with the configured bind account. I think we noticed this, but didn't think this would be related to our issue, as our VendorLDAP was working correctly.

 

After thinking about your comment about the sync issue, we enabled LDAP debug to get some more information (following Enable Debugging and Gather Logs - LDAP tracing on the Vault (cyberark.com))

 

On the trace.d0 logs, I found that when logging into the PVWA with a new RPAM Vendor account (which was not previously created), I could see a logon to the main LDAP directory, this failed due to the authentication issue, and as such, it just died before being able to logon to the VendorLDAP directory.

 

We're still trying to figure out why this bind account no longer is working. We've used ldp.exe and it looks like this user/pass combination we had is fine. The AD team says they've done nothing, except the account was modified right around the time it started failing.

 

I'll update when I know what is going on with this bind account, however, looks like this LDAP failure causes the failure for the RPAM side, which I was not aware of could be affected.

 

Chris

  • 626 Views
  • 2 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!