Novell ACCESS MANAGER 3.1 SP2 - README 2010, Руководство пользователя

Страница: 295 / 374

Configuring Liberty Web Services 295
n
ov
do
cx (e
n)
16
Ap
ril 20
10
Selected Write Locations: The list of selected locations to write attribute data to. If you add
multiple entries to this list, the system searches attributes in each location in the order you
specify. When a match is found for an attribute, the other locations are not searched. Use the
up/down and left/right arrows to control which locations are selected and the order in which
they are selected.

Configuration Datastore: Liberty attribute values can be stored in the configuration store
of the Administration Console. The Identity Server can write values to these attributes. If
this location appears first in the list of
Selected Write Locations , all Liberty attribute
values are written to this location. If you want values written to the LDAP user store, the
LDAP Data Mappings location must appear first in the list.

LDAP Data Mappings: If you have mapped a Liberty attribute to an LDAP attribute in
your user store, the Identity Server can write values to the attribute in the LDAP user
store. To create LDAP attribute maps, see
Section 13.6, “Mapping LDAP and Liberty
Attributes,” on page 304 .
Available Write Locations: The list of available locations to write attributes containing
profile data. Locations in this list are currently not being used.
6 (Optional) Specify data model extensions.
Data Model Extension XML: The data model for some Web services is extensible. You can
enter XML definitions of data model extensions in this field. Data model extensions hook into
the existing Web service data model at predefined locations.
All schema model extensions reside inside of a schema model extension group. The group
exists to bind model data items together under a single localized group name and description.
Schema model extension groups can reside inside of a schema model extension root or inside
of a schema model extension. There can only be one group per root or extension. Each root is
hooked into the existing Web service data model. Multiple roots can be hooked into the same
location in the existing Web service data model. This conceptual model applies to the structure
of the XML that is required to define data model extensions.
See
Appendix C, “Data Model Extension XML,” on page 369 for more information.
7 Click OK , then click OK on the Web Service Provider page.
8 Update the Identity Server.
13.2.2 Modifying Details for Authentication, Discovery, LDAP,
and User Interaction Profiles
This page allows you to specify information for Discovery, LDAP, and User Interaction Web service
profiles. If you are creating a Web service type, this is Step 2 of the Create Web Service Wizard.
For conceptual information about profiles, see Managing Web Services and Profiles .
1 In the Administration Console, click Devices > Identity Servers > Edit > Liberty > Web Service
Provider > [Profile] .
2 Click Authentication, Discovery, LDAP, or User Interaction , depending on which profile you
want to edit.
3 Configure the following fields:
Display name: The Web service name. This specifies how the profile is displayed in the
Administration Console.