Avaya Administering Aura Session Manager Release 6.1 Manual de usuario descargar pdf (Pagina 123)

enterprise directory entry. If it does not exist, synchronization rules can be used

to populate it for other fields e.g. Surname, GivenName, or LoginName.

displayNameAscii:The full text name of the user represented in ASCII. It is used

to support display (e.g. endpoints) that cannot handle localized text.

dn:The distinguished name of the user. The DN is a sequence of relative

distinguished names (RDN) connected by commas. An RDN is an attribute with an

associated value in the form of attribute=value, normally expressed in a UTF-8

string format.The dn can be used to identify the user and may be used for

authentication subject mapping. Note the dn is changeable.

isDuplicatedLoginAllowed:A boolean indicator showing whether this user is

allowed a duplicate concurrent logins.A true stipulates that the user is allow to

have duplicate logins. Default value is true.

isEnabled:A boolean indicator showing whether or not the user is active. Users

with AuthenticationType equals Basic will fail if this value is false.This attribute

can be used to disable access between login attempts. A running sessions login will

not be revocable. Alternatively the administrator can always modify the password to

disable the user from logging in.A true stipulates this is an active user, a false

used for a disabled user. Default value is false.

isVirtualUser:A boolean indicator showing whether or not the record is being

used for a non-human entity such as an application, service, software agent, etc.

This is to be used where the entity will behave as a user and needs to have subset

of the user profile populated. If the entity does not behave as a user and has a

different trust relationship e.g. a trust certificate it should not be treated as a

virtual user. A virtual user can represent an Avaya or external non-human entity.

This attribute is provided as a convenience to track such accounts.A true stipulates

this is a virtual users, a false is used for human users. Default value is false.

givenName:The first name of the user.

honorific:The personal title used to address a user. This is typically a social

title and not the work title which is contained in the title attribute. This

attribute can map to PersonalTitle.

loginName:This is the unique system login name given to the user. It can take

the form of username@domain or just username.This may vary across customers. It can

be used to help provision default user handles in the CSHandle table.The username

is an alphanumeric value that must comply with the userinfo related portion of a URI

as described in rfc2396. However, it is further restricted as ASCII characters with

only the _ and . special characters supported. This is the rfc2798 uid attribute.

middleName:The middle name of the user

managerName:Text name of the users manager. This is a free formed field and does

not require the users manager to also be a user of the solution. This attribute was

requested to support reporting needs.

preferredGivenName:The preferred first name of the user.

preferredLanguage:The individuals preferred written or spoken language.Values

will conform to rfc4646 and the reader should refer to rfc4646 for syntax.This

format uses the ISO standard Language ISO639 and region ISO3166 codes In the absence

of a value the clients locale should be used, if no value is set, en-US should be

defaulted.

source:Free format text field that identifies the entity that created this user

record. The format of this field will be either a IP Address/Port or a name

representing an enterprise LDAP or Avaya.

sourceUserKey:The key of the user from the source system. If the source is an

Enterprise Active Directory server, this value with be the objectGUID.

status:This information is to help manage provisioning activities such as

correcting or completing the provisioning of a user instance. It can also signify

that approval is needed (PENDINGAUTHZ) before a user account is sufficiently

configured to be a valid user (PROVISIONED). Possible Values:

AUTHPENDING;PENDINGAUTHZ;PROVISIONED

suffix:The text appended to a name e.g. Jr., III.

surname:The users last name, also called the family name.

timeZone:The preferred time zone of the user. For example: (-12:0)

International Date Line West.

title:The job function of a person in their organizational context.

userName:This is the username portion of the loginName field. It is an

alphanumeric value that must comply with the userinfo related portion of a URI as

described in rfc2396. However, it is further restricted as ASCII characters with

only the _ and . special characters supported. This is the rfc2798 uid attribute.

Managing bulk importing and exporting

Administering Avaya Aura

Session Manager November 2010 123

1 2 ... 118 119 120 121 122 123 124 125 126 127 128 ... 531 532

Avaya Administering Aura Session Manager Release 6.1 Manual de usuario Pagina 123

Comentarios a estos manuales

Avaya Administering Aura Session Manager Release 6.1 Manual de usuario Pagina 123

Comentarios a estos manuales

Relacionado con productos y manuales para Software Avaya Administering Aura Session Manager Release 6.1