Versions Compared

Old Version 6

changes.mady.by.user Kim Rasmussen

Saved on

compared with

New Version 7

changes.mady.by.user Jesper Nielsen

Saved on

Key

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

...

Some plugins can be added to the user administration server to serve for example infrastructure purposes or allow other systems to be notified on certain changes.

PropertyValue
user.attribute

A class name of a class impementing the dk.itp.portalprotect.useradmin.plugin.IUserAttributeValidator interface which will be called to check if it is allowed to update, insert or delete certain attributes (or values thereof) on a user.

The class can also be used to notify other systems of changes if needed

user.attributelist

A class name of a class implementing the dk.itp.portalprotect.useradmin.plugin.IAttributeList.

This class must return a list of attribute names that is allowed to change no a user obbject from the user administration client - so this can be controlled centrally.

By default the user administration client will allow changes to all user attributes (pending ACL check)

user.postcreate

A class name of a class implementing the dk.itp.portalprotect.useradmin.plugin.IUserCreate interface.

The class will be called when the user has been created. This can for example be used to notify other systems that a user has been created.

user.precreate

A class name of a class implementing the dk.itp.portalprotect.useradmin.plugin.IUserCreate interface.

The class will be called to check if it is allowed to create the user with the given logon id and credentials. 

organisation.attributeslist

A class name of a class implementing the dk.itp.portalprotect.useradmin.plugin.IAttributeList.

This class must return a list of attribute names that is allowed to change on an organisation from the user administration client - so this can be controlled centrally.

By default the user administration client will allow changes to all organisation attributes (pending ACL check)


This section relates to the multi schema functionality, used to keep different users in the database physically seperated by using different schemas.

Property

Value

schema.enable

<true/false>

Enables the multi schema support for the user admin server - allowing users of the API to define through the "getInstance" or "getSchemaInstace" which schema to access and store users.

False is the default value

schema.instance.root

<root schema name> 

The root schema name used when "schema.enable" is set to true. This schema name will be used when "null" is given as the instance name to the "getInstance" or "getSchemaInstace" methods on the user admin API. 

The value must be set if the property "schema.enable" is set to true. For the sample derby database provided with the Ceptor installation, "APP" is the schema name to provide here.

schema.instance.XXX

<schema name for instance XXX> 

The schema name used when "schema.enable" is set to true for a given instance XXX. This schema name will be used when "XXX" is given as the instance name to the "getInstance" or "getSchemaInstace" methods on the user admin API. 

The value must be set for each of the schemas/instances used in the API.