Configure the EAServer realm

The EAServer CSI realm plugs in to an EAServer application server. Its purpose is to delegate authentication and authorization checks to the security provider.

Setting up the EAServer realm

1. To debug the CSI realm, create a file called log4j.properties in %JAGUAR%\java\classes, where JAGUAR is the EAServer installation directory, and insert the following text, which causes debug and log messages to be written to %JAGUAR%\bin\Jaguar.log:

   log4j.appender.RootAppender=org.apache.log4j.ConsoleAppender
   log4j.appender.RootAppender.layout=org.apache.log4j.PatternLayout
   log4j.appender.RootAppender.layout.ConversionPattern=%d{ISO8601} 
      %-5p %-25c{1} %x - %m%n
   log4j.rootCategory=WARN, RootAppender
   log4j.category.com.sybase.security=DEBUG
   

2. To use the PortalDB security provider only, skip to step 4.

   If you are using the LDAP security provider, the EAServer CSI realm does not validate the LDAP provider’s XML configuration file against the schema. To validate the XML configuration file:

   1. Verify that the JVM supports Java API for XML Processing (JAXP) 1.2 or higher.

   2. Configure the XML validation property:

      1. In EAServer Manager, expand the Servers folder, highlight Jaguar, and select File | Properties. The Server Properties dialog box displays.

      2. On the Advanced tab, click Add, then enter com.sybase.security.core.XmlConfiguration.XmlValidation as the property name and “true” as the property value.

         Click OK.

3. Configure the security provider—see “Configuring the security provider”.

4. Restart EAServer. In EAServer Manager, highlight Jaguar, and select File | Shutdown and Start.

Copyright © 2004. Sybase Inc. All rights reserved.

View this book as PDF