Cloud CM-IPMP Guía para resolver problemas Pagina 102

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 201
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 101
The file config/ldapauth.properties contains configuration for the LDAP connection, please see the Rhino Javadoc for
com.opencloud.rhino.security.auth.LDAPLoginModule. Here is a sample configuration.
rhino.security.auth.ldap.host=host.domain
rhino.security.auth.ldap.port=389
rhino.security.auth.ldap.binddn=
rhino.security.auth.ldap.bindpw=
rhino.security.auth.ldap.basedn=O=OpenCloud,OU=Research Development
rhino.security.auth.ldap.usetls=true
3. ProfileLoginModule
The login credentials and roles are stored in a SLEE profile table.
jaas-context {
com.opencloud.rhino.security.auth.ProfileLoginModule REQUIRED
profiletable="Users" hash="md5";
};
The ProfileLoginModule works by looking up a profile with a name matching the supplied username in a specified table.
It then compares the supplied password with the password stored in the profile. If the authentication succeeds, it retrieves
the roles for that user from the profile.
The ProfileLoginModule supports the following options:
(a) profiletable - the name of the profile table to use (defaults to "UserLoginProfileTable")
(b) passwordattribute - the profile attribute to compare the password against, attribute type must be java.lang.String
(defaults to "HashedPassword")
(c) rolesattribute - the profile attribute to load the roles from, attribute type must be array of java.lang.String (defaults
to "Roles")
(d) hash - the hashing algorithm to use for the password, may be "none" or "md5" (defaults to "md5")
A profile specification is provided with Rhino that can used to create a profile table for the profile login module. A
profile table named "UserLoginProfileTable" created using the provided profile specification will work with all the default
configuration values listed above.
It is recommended that a file login module be configured as a fallback mechanism in case the profile table is accidentally
deleted/renamed or the the admin user profile is deleted/changed. (It would not be possible to fix the problem with
the profile table since no user would be able to login using a management client.) This can be achieved by giving the
ProfileLoginModule a "SUFFICIENT" flag and the FileLoginModule a "REQUIRED" flag. (See the JAAS Javadoc for
more details about these flags.)
jaas-context {
com.opencloud.rhino.security.auth.ProfileLoginModule SUFFICIENT
profiletable="Users" hash="md5";
com.opencloud.rhino.security.auth.FileLoginModule REQUIRED
file="/home/rhino/config/passwd" hash="none";
};
Open Cloud Rhino 1.4.3 Administration Manual v1.1 93
Vista de pagina 101
1 2 ... 97 98 99 100 101 102 103 104 105 106 107 ... 200 201

Comentarios a estos manuales

Sin comentarios