Appendix B: Setting Up Authentication and Authorization

Restore the PortalDB provider configuration

Initially, Enterprise Portal is configured to use the PortalDB security provider. If your system was changed to use the LDAP security provider, you can restore the PortalDB configuration using the following procedure.

Change to the location of the global.properties.xml file, either:
- Tomcat – %SYBASE%\infoedition\tomcat\webapps\onepage\config, where SYBASE is the root installation directory of your Sybase software, or
- EAServer – %JAGUAR%\Repository\WebApplication\onepage\config, where JAGUAR is the EAServer root installation directory.
Using a text editor, open global.propeties.xml, and set the value of the AuthenticationUsing property to “Database”.
Change to the location of the csi.xml file, either:
- Tomcat – %CATALINA_HOME%\conf, where CATALINA_HOME represents the Tomcat root installation directory, or
- EAServer – %JAGUAR%\Repository\Component\csi-easerver
Open csi.xml, and verify that the PortalDB provider definitions are not commented out. The sample csi.xml file that is installed with Enterprise Portal contains the following PortalDB provider definitions:
```
<config:authenticationProvider    name="com.sybase.security.portaldb.PortalDBLoginModule"    controlFlag="optional">

   <config:options name="DatasourceName"       value="java:comp/env/jdbc/portaldb" />

</config:authenticationProvider>

<config:provider name=”com.sybase.security.portaldb.PortalDBAttributer”    type=”attributer” />
```
The value of DatasourceName defines the name that is passed to the javax.naming.InitialContext().lookup(datasourceName) method to retrieve a connection to the portaldatabase. The default value is “java:comp/env/jdbc/portaldb,” and Enterprise Portal creates this JNDI name automatically during deployment. If the DatasourceName configuration option is missing, the default value is used.

To use the PortalDB provider only, comment out the LDAP provider definition in csi.xml. To comment out the definition, insert “” at the end of the definition. In the following example, the LDAP provider definition is commented out:

<!--
<authenticationProvider name=”com.sybase.security.ldap.LDAPLoginModule”>
   <options name=”ServerType” value=”sunone5”/>
   <options name=”DefaultSearchBase” value=””/>
   <options name=”ProviderURL” value=”ldap://localhost:389”/>
   <options name=”AuthenticationMethod” value=”simple”/>
   <options name=”AuthenticationScope” value=”subtree”/>
   <options name=”AuthenticationSearchBase” value=””/>
   <options name=”RoleScope” value=”subtree”/>
   <options name=”RoleSearchBase” value=””/>
</authenticationProvider>
-->

To use both the PortalDB provider and the LDAP provider, verify that neither of the provider definitions is commented out.

View this book as PDF