User administration

Last Updated : Oct 07, 2020 |
Prolog information
Metadata
Keywords:
Consider the following recommendations:
  1. Avaya recommends that a user’s Presence/IM address is equal to the user’s e-mail address. For example:
    • User: John Smith
    • Presence/IM address: jsmith@example.com
    • e-mail address: jsmith@example.com
    Microsoft RTC deployments follow this approach. New Avaya PMM deployments should not have difficulties to follow this approach.
  2. Alternatively, Presence/IM address domains and e-mail address domains must not overlap. For example:
    • User: John Smith
    • Presence/IM address: jsmith@pmm.example.com
    • e-mail address: jsmith@example.com
    Federated XMPP deployments typically follow this approach.
In deployments with federation, the Presence/IM addressing approach has to be consistent across federated solutions. For example, if a solution consists of an Avaya PMM solution federated with an Microsoft RTC solution, both Avaya and Microsoft solutions must take the same approach. You will not experience any functional differences between the two approaches.
Additionally, you must follow the below guidelines:
Task
Guidelines
Administering Presence/IM service to solution users
Administer only one service to a user:
  • Administer Avaya PMM service to Avaya users using System Manager.
  • Administer the federated Presence/IM service to Federated users using the appropriate Management Tool of the federated system.
This minimizes the overall administration work and overall number of user-level licenses required. Solutions users include Avaya Aura® users and the federated system users.
Administering Presence/IM address to solution users
Administration of the Presence/IM address to a user is part of administering the Presence/IM service to the user.
  • For Aura users, this is done in System Manager user management by assigning an “Avaya Presence/IM Communication Address” to the user. The Presence/IM address can be administered with a value different than the user’s e-mail address.
  • For Federated users, this is done in the appropriate Management Tool of the federated system. Most of the third-party Presence/IM solutions allow the Presence/IM address to be administered with a value different than the user’s e-mail address.
Note:
You must follow one of the recommendations during Presence/IM address assignment.
Administering Presence/IM users in the Enterprise Directory
  • Every solution user must be defined in the Enterprise Directory. This is to facilitate ease of finding a user and initiating different modes of communication with the user without needing to manually enter a specific address required to reach the user.
  • This recommendation is given in such a way to enable multiple-domain environments.
  • User data in the Enterprise Directory must include an attribute whose value indicates the exact Presence/IM address of the user.
  • In the Avaya documents, the selected attribute is referred to as the DIRIMATTRIBUTE.
  • In the Avaya PMM solution, a configuration parameter is used to define the value of the DIRIMATTRIBUTE such as the name of the Directory attribute that holds the exact Presence/IM address of a user.
    Note:
    Another Avaya configuration parameter – DIRUSEIMDOMAIN – must be set to 0 (false).
  • The designated directory attribute must be populated with the exact Presence/IM address of the user.
    • For Avaya users, the value must equal the “Avaya Presence/IM” address value as administered in System Manager.
    • For Federated users, the value must be equal Presence/IM address value administered to the user in the appropriate Management Tool of the federated system.
  • If the Recommendation #1 is followed, the good candidate for the DIRIMATTRIBUTE is the e-mail attribute. For example, mail is the default Avaya value.
  • If the Recommendation #2 is followed, there might not be an existing directory attribute that contains the exact Presence/IM address of the user. In such a case, the Directory schema may need to be extended by introduction of a new extension attribute and the attribute populated with the appropriate value for every user.

IWA support

IWA can be used for users in the domain or sub-domain of the default enterprise directory. Administrators must ensure that the keytab provided to the server is generated for the default directory service. In addition, the client of these users must be enabled to use IWA. This can be done by setting SUPPORTWINDOWSAUTHENTICATION property to 1 in the client settings file. For all other domain users, this value must be set to 0. For more information, see REST API clients authentication.