000026095 - How to use RSA ClearTrust Administrative API for custom authentication/authorization

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000026095
Applies ToRSA ClearTrust 5.5 Administrative Java API
RSA ClearTrust 5.5.1 Administrative Java API
RSA ClearTrust 5.5.2 Administrative API
IssueHow to use RSA ClearTrust Administrative API for custom authentication/authorization
Transport and Null Pointer Exceptions in RSA ClearTrust eserver.log
eserver.log shows intermittent exceptions: "java.net.SocketException: Broken pipe" or "messageID=-2,internal_error,description='Broken pipe',details='sirrus.util.serialization.SerializationException: Broken pipe'", followed by a large number of NullPointerException's
CausePrior to RSA ClearTrust 5.5.3, the Entitlements Server and the Administrative API had fundamental performance limits due to the architecture. Customers using the Administrative API for large volumes of authentication/authorization, or using the Entitlements Manager under heavy load, experienced socket timeouts and dropped connections. The Entitlements Server and the Administrative API were not designed to handle volumes comparable to the authorization server or the Runtime API.
ResolutionPart of the purpose of the RSA ClearTrust 5.5.3 patch was to address those performance limits. While the fundamental architecture was not changed, many performance improvements were made to allow fand higher volumes of traffic against the entitlements server or Administrative API.

Applying the 5.5.3 patch can mitigate performance problems for situations where the Entitlements Manager is in wide use, or where the Administrative API is under heavy concurrent load.
Legacy Article IDa24612

Attachments

    Outcomes