Versions Compared

Old Version 2

changes.mady.by.user Former user

Saved on

compared with

New Version 3

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section
Column

Sometimes, is deployed to an existing servlet container that is already handling user authentications through, for instance, LDAP. Here the authentication is the responsibility of the container, but is still responsible for the runtime authorization and the design time querying of user metadata. The LDAP Container Security Manager reuses the existing LDAP connector but relies on the container for user authentications.

 

 

Column
width300px

On this page:

Table of Contents
maxLevel2

...

  1. Stop  if it is running.
  2. Modify the <frevvo-home>\tomcat\conf\server.xml file. Here is an example of the changes needed when using tomcat.
    1. Edit this file with a text editor.
    2. Search for 'ldap://localhost:389 - you should find this in the org.apache.catalina.realm.JNDIRealm section of the file. 
    3. Notice lines 98 - 107 are commented out.
    4. Uncomment this section. Replace the existing code with the code shown below: 
    5. Replace the connectionURL, connectionName and the connectionPassword default values with your LDAP server information. 
    6. Refer to this website for detailed information about the remaining parameters.

...

      3. Configure LDAP - The LDAP Container Security Manager uses the LDAP Security Manager so the setup for both is the same. LDAP Security Manager configuration is done via the UI when you  
Here is a Sample LDAP Configuration: notice the ldap connection url, name and password have been changed to specify the LDAP server name and the administrator id/password. 

...

you add the tenant.
      4. Start .

      5. Create a tenant with the LDAP Container Security Manager class.

...