com.sun.xml.ws.api.security.trust.WSTrustException

Error validating SAM L Assertion signature at epsos.ccd.netsmart.securitymanager.sts.STSService.getIdAssert ionFromHeader(STSService.java:268) at epsos.ccd.netsmart.securitymanager.sts.STSService.invoke(STSS ervice.java:157) at epsos.ccd.netsmart.securitymanager.sts.STSService.invoke(STSS ervice.java:87) at com.sun.xml.ws.api.server.InstanceResolver$1.invokeProvider(I nstanceResolver.java:256) at com.sun.xml.ws.server.InvokerTube$2.invokeProvider(InvokerTub e.java:156) at com.sun.xml.ws.server.provider.SyncProviderInvokerTube.proces sRequest(SyncProviderInvokerTube.java:78)

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web1

  • via JIRA by Kostas Karkaletsis, 11 months ago
    Error validating SAM L Assertion signature at epsos.ccd.netsmart.securitymanager.sts.STSService.getIdAssert ionFromHeader(STSService.java:268) at epsos.ccd.netsmart.securitymanager.sts.STSService.invoke(STSS
  • Stack trace

    • com.sun.xml.ws.api.security.trust.WSTrustException: Error validating SAM L Assertion signature at epsos.ccd.netsmart.securitymanager.sts.STSService.getIdAssert ionFromHeader(STSService.java:268) at epsos.ccd.netsmart.securitymanager.sts.STSService.invoke(STSS ervice.java:157) at epsos.ccd.netsmart.securitymanager.sts.STSService.invoke(STSS ervice.java:87) at com.sun.xml.ws.api.server.InstanceResolver$1.invokeProvider(I nstanceResolver.java:256) at com.sun.xml.ws.server.InvokerTube$2.invokeProvider(InvokerTub e.java:156) at com.sun.xml.ws.server.provider.SyncProviderInvokerTube.proces sRequest(SyncProviderInvokerTube.java:78) at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:637) at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:596) at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:581) at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:478)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.