web server - Borland Technical Publications

Security management with the Security Map
Authorization domain
The element in the ra-borland.xml descriptor file specifies the
authorization domain associated with a specified user role. If is set, you
should set with its associated domain. If
is not set, VisiConnect assumes the use of the default authorization domain.
See the Security Guide for more information on using authorization domains.
Default roles
In addition, the element enables the definition of a default user role that
can be associated with the appropriate resource role. This default role would be
preferred to if the user role identified at run-time is not found in the mapping. The
default user role is defined in the element with a element
given a value of “*”. For example:
*
A corresponding entry must be included in the element.
The following example illustrates the association between a Borland Enterprise Server
user role and a resource role.
*
SHME_OPR
The default user role is also used at deployment time if the connection pool parameters
indicate that the Borland Enterprise Server should initialize connections. The absence
of a default user role entry or the absence of a element may prevent the
server from creating connections using container-managed security.
Generating a resource vault
To use run-as security mapping as described above, a resource role(s) must be
defined in a vault which is provided to the Borland Enterprise Server. This is known as
the resource vault.
VisiConnect provides a tool, ResourceVaultGen, to create a resource vault and to
instantiate role objects in this vault. A role name and its associated security credentials
are written to the resource vault by ResourceVaultGen. At this time only credentials of
type Password Credential can be written to the resource vault. The usage of
ResourceVaultGen is as follows:
java -Dborland.enterprise.licenseDir= -
Dserver.instance.root=
com.borland.enterprise.visiconnect.tools.ResourceVaultGen -rolename
-username -password -vaultfile
-vpwd
Chapter 27: Using VisiConnect 261