Delegating EAServer Security to a Third-Party Provider

If you choose not to use the Basic Provider Suite that comes preconfigured with the common services layer, you can delegate EAServer security included in Service Container to a supported third-party security provider (for example, LDAP, RADIUS, or Certificate) by configuring the default.xml file.

Each file configures delegation to only one provider. Each provider should have its own configuration, even if multiple providers are of the same type. LDAP and the BPS providers can host the certificate provider. If one of them does, you must configure LDAP or BPS in addition to a certificate provider

  1. Stop the EAServer.
  2. Modify the sample default.xml file to delegate security to LDAP, RADIUS, or Certificate: <installation directory>\EAServer\Repository\CSI\conf\default.xml

    Different providers have different options you can set. Each of these options are documented in the appropriate Configuration Properties topic in this module.

  3. Save and close the default.xml file.
  4. Restart the EAServer.
Parent topic: Third-Party Provider Security
Related concepts
LDAP Security
Certificate Security
RADIUS Security
Service Container Security Planning
Native Basic Provider Suite Security
Related reference
LDAP Configuration Properties
RADIUS Configuration Properties
Certificate Configuration Properties
BPS Configuration Properties

Send your feedback on this help topic to Sybase Technical Publications: pubs@sybase.com

Your comments will be sent to the technical publications staff at Sybase, Inc. For product-related issues or technical support, contact Sybase Technical Support at 1-800-8SYBASE.