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

userPassword:The encrypted password for this users account.A null password is

used when the user is authenticated by the enterprise such as with a separate source

such as the enterprise LDAP.

commPassword:The encrypted subscriber or communication password with which the

user logs can use to authentication with on to any CommProfile SIP and non SIP.

This attribute is meant to be a shared across different communication profiles and

thus different communication services.

userType:This enumerates the possible primary user application types. A User can

be associated with multiple user types. Possible values are

ADMINISTRATOR;COMMUNICATION USER;AGENT;SUPERVISOR;RESIDENT EXPERT;SERVICE

TECHNICIAN;LOBBY PHONE

roles:Text name of a role.This value needs to pre-exist in SMGR DB

address:The address of the user.

securityIdentity:The SecurityIdentity is used to hold any additional identities

for a user that can be used for authentication such as their loginName, Kerberos

account name, or their X509 certificate name.

ownedContactLists:It is a collection of internal or external contacts.

ContactList is owned by a specific user and has a name that a unique name within the

context of its owner.

ownedContacts:It represents a non Avaya application user (external) contact.

Contacts can be collected together along with User entities into a contact list.

Contacts can be created by an administrator or an end user.

presenceUserDefault:These are personal rules that are set by presentities to

define how much presence information can be shown to watchers that are not

explicitly mentioned in an ACL. There may be one User Default rule per presentity

(User), or none.

presenceUserACL:These are personal rules defined by presentities themselves on

who can monitor their presence information. There may be several entries in the list

for a given presentity, each entry corresponding to one watcher.

presenceUserCLDefault:This is a personal rule that is set by presentities to

define how much presence information can be shown to watchers that belong to the

userss contact list. There may be one User Contact List Default rule per presentity

(Person) or none.

commProfileSet:A user will have a default commprofile set.A commprofile set can

exist without any handles or commprofiles referencing it. I.e. you can create a

commprofile set without needing to also create either a handle or a commprofile.A

commprofile set can contain multiple commprofiles, but only one of each specific

type. This is enforced by having the CSCommProfile uniqueness constraint include

type, cs_commprofile_set_id.

-->

<tns:user>

<authenticationType>BASIC</authenticationType>

<description>this is description</description>

<displayName> John Miller</displayName>

<isVirtualUser>false</isVirtualUser>

<loginName>[email protected]</loginName>

<managerName>Jay Smith</managerName>

<preferredLanguage>English</preferredLanguage>

<status>AUTHPENDING</status>

<surname>Miller</surname>

<timeZone>(-12:00) International Date Line West</timeZone>

<userName>jmiller</userName>

<userPassword>password</userPassword>

Managing Users

124 Administering Avaya Aura

Session Manager November 2010

Comments? [email protected]

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

Comentarios a estos manuales

Sin comentarios

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

Comentarios a estos manuales

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