# \[ERROR\] UascServerAsymmetricHandler **URL:** \ **Category:** Ignition Early Access\ **Created:** [January 11, 2019, 9:17am UTC](https://forum.inductiveautomation.com/t/error-uascserverasymmetrichandler/21810 "2019-01-11T09:17:06Z")\ **Posts on this page:** 1\ **Showing post:** 13
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [August 28, 2019, 8:23pm UTC](https://forum.inductiveautomation.com/t/error-uascserverasymmetrichandler/21810/13 "2019-08-28T20:23:37Z")
Okay. Well, you need to make sure Ignition’s client certificate is trusted in KSE. You also need to make sure KSE’s server certificate is trusted in Ignition. It’s on the gateway under Configure \> OPC UA \> Security. Then go to the _Client_ tab and you should see the KSE server certificate there with a button to mark it as trusted. Then, after all this, there’s a possibility you’re running a version of KSE with a bug that generates invalid application URIs in the certificate. This manifests as a Bad\_CertificateUriInvalid error, the same as described in [this post](http://forum.inductiveautomation.com/t/mx-opc-application-uri/27735). If this is happening you need to upgrade KSE to a 6.1+ version and generate the certificate. --- _[View the full topic](https://forum.inductiveautomation.com/t/error-uascserverasymmetrichandler/21810)._