Cloudscape Properties
Page 6 of 47

cloudscape.authentication.provider

Function

Specifies the authentication provider for Cloudscape user authentication.

Legal values include:

  • LDAP

    An external LDAP directory service.

  • NIS+

    An external NIS+ directory service.

  • CLOUDSCAPE

    Cloudscape's simple internal user authentication repository.

  • a complete Java class name

    A user-defined class that provides user authentication.

When using an external authentication service provider (LDAP or NIS+), you must also set:

When using LDAP, you can set other LDAP-specific properties. See also:

Alternatively, you can write your own class to provide a different external authentication service. This class must implement the public interface COM.cloudscape.authentication.Interface.AuthenticationScheme and throw exceptions of the type COM.cloudscape.authentication.Interface.AuthenticationException where appropriate. Using a user-defined class makes Cloudscape adaptable to various naming and directory services. For example, the class could allow Cloudscape to hook up to an existing user authentication service that uses any of the standard directory and naming service providers to JNDI.

To enable any Cloudscape user authentication, you must set the cloudscape.connection.requireAuthentication property to true.

For more information about user authentication, see Working with User Authentication of the Cloudscape Developer's Guide.

Syntax

cloudscape.authentication.provider={
    LDAP |
    NIS+ |
    CLOUDSCAPE |
    classProviderName }

Example

-- system-wide property
cloudscape.authentication.provider=LDAP

-- database-wide property
CALL PropertyInfo.setDatabaseProperty(
    'cloudscape.authentication.provider',
    'CLOUDSCAPE')

-- publishing a database-wide property
CREATE PUBLICATION APub
ADD TARGET DATABASE PROPERTY cloudscape.authentication.provider=
    'NIS+'

Scope

system-wide

database-wide (publishable)

Dynamic or Static

Static. For system-wide properties, you must reboot Cloudscape for the change to take effect. For database-wide properties, you must reboot the database for the change to take effect.