Managing users - How it works

External / Internal

The portal shows 2 lists of users: Internal and External by the value of the field UsercloudType

The UsercloudType is set based on internal domain list.

For Webex the adapter will update the UsercloudType . If changes are done later in the portal- the portal will update the type.

 

Webex only:

Every day the adapter asks for all users from Webex. If use is not retrieved for 10 days, it will deleted -only for internal users.

This is done to avoid inspecting internal users that have left

MS Teams Proxy

While working with Proxy- The user table includes all the users that have communication detected by the proxy. In show 2 separate views:

  1. Users - all users from the internal domain list

  2. External- all other users

In the users list, the MNTS updates if the user is managed or not by reviewing the auditing table.

Each record in the Auditing that the scope is meeting and the activity is Audio has a managed user in the From field.

 

While working with Proxy more details on IP and last login as be see in the details

 

Note:

In some cases, the system does not get the UPN from external users (typically not federated) and needs to allocate a UPN based on the display name to give some information on the user

In such case , the user name will start with the prefix “DisplayName-” following by the display name shown in the client.

 

Understand how the TP gets user info - https://agatsoftware.atlassian.net/wiki/spaces/SKYP/pages/1679917319

 

Webex Teams API deployment

While working with Webex Teams API- The user table includes all the users that have communication detected by the API.
The portal displays 2 separate views:

  1. Users - all users from the internal domain list

  2. External- all other users

Webex Teams API inserts the email addresses of the users to the users table.

The MNTS updates internal users information according to the email from Webex Teams API.
It updates the following:

UPN , Display name, Domain, User Cloud ID , User cloud Type (internal / External), Lastupdated (the time it was updated)

User Cloud ID is fetched from Azure as a guid and from Local AD it is the username .


Internal users are determined by the domain in the email address.