Methods and systems for multi-tenant controller based mapping of device identity to network level identity

1. A method comprising:

executing at a controller a horizontally scalable service Identity Definitions Manager (IDM) Service;

mapping active directory (AD) domains to WAN network elements DNS ROLE and LDAP ROLE;

instructing a plurality of network elements associated with a tenant to discover a plurality of AD domains and AD servers in an enterprise using the DNS ROLE;

receiving from the plurality of network elements running DNS ROLE information indicative of changes to network attributes selected from the group consisting of AD domains, additions and subtractions of AD servers and changes in an IP address of AD servers;

transmitting the received AD domains and AD servers to a tenant administrator and requesting credentials to communicate with added AD servers using LDAP;

executing an algorithm to determine which element will contact specific AD instances to

minimize lightweight directory access protocol (LDAP) traffic volume occurring on the WAN and to ensure AD instances can still be reached in case of failure of any one network element;

monitoring in Active Directory servers changes in at least one identity of a network user by using the LDAP ROLE on the network elements; and

updating a policy, based at least in part on the mapping of user identity in AD domains, at a multi-tenant controller, wherein the tracking of changing identity information is implemented as a horizontally scalable service the Identity Definitions Manager Service.

2. The method of claim 1 further employing a multi-tenant controller based mapping of a user or device identity to a network level identity.

3. The method of claim 1 further comprising performing application analysis on a per session basis.

4. The method of claim 1 further comprising routing traffic based, at least in part, on a dynamic and automated QoS definition.

5. The method of claim 4 further comprising employing on the traffic modeling and analytics selected from the group consisting of Pareto and Weibull.

6. The method of claim 1 further comprising employing QoS standardized controls selected from the group consisting of shaping, policing, random early discard, tail drop, low latency queues, fair queues, anomaly queues and buffers.

7. The method of claim 1 further comprising utilizing a network identity type.

8. A centrally controllable multi-tenant controller for controlling a plurality of assets across a plurality of distributed computing environments wherein the controller is configured to:

execute at a controller a horizontally scalable service Identity Definitions Manager (IDM) Service;

map active directory (AD) domains to WAN network elements DNS ROLE and LDAP ROLE;

instruct a plurality of network elements associated with a tenant to discover a plurality of AD domains and AD servers in an enterprise using the DNS ROLE;

receive from the plurality of network elements running DNS ROLE information indicative of changes to network attributes selected from the group consisting of AD domains, additions and subtractions of AD servers and changes in an IP address of AD servers;

transmit the received AD domains and AD servers to a tenant administrator and requesting credentials to communicate with added AD servers using LDAP;

execute an algorithm to determine which element will contact specific AD instances to minimize lightweight directory access protocol (LDAP) traffic volume occurring on the WAN and to ensure AD instances can still be reached in case of failure of any one network element;

receive, using the LDAP ROLE of network element, changes in Active Directory servers in at least one of a user identity and a group identity of a network; and

update a policy, based at least in part on the mapping of user identity in AD domains, at a multi-tenant controller, wherein the tracking of changing identity information is implemented as a horizontally scalable service the Identity Definitions Manager Service.

9. The centrally controllable multi-tenant controller of claim 8 further configured to employ a multi-tenant controller based mapping of a user or device identity to a network level identity.

10. The centrally controllable multi-tenant controller of claim 8 further configured to perform application analysis on a per session basis.

11. The centrally controllable multi-tenant controller of claim 8 further configured to route traffic based, at least in part, on a dynamic and automated QoS definition.

12. The centrally controllable multi-tenant controller of claim 11 further configured to employ on the traffic modeling and analytics selected from the group consisting of Pareto and Weibull.

13. The centrally controllable multi-tenant controller of claim 8 further configured to employ QoS standardized controls selected from the group consisting of shaping, policing, random early discard, tail drop, low latency queues, fair queues, anomaly queues and buffers.

14. The centrally controllable multi-tenant controller of claim 8 further configured to utilize a network identity type.

15. A method comprising:

executing at a controller a horizontally scalable service IP to Site Mapping (ISM) Service;

instructing a plurality of network elements associated with a tenant to discover a plurality of AD domains and AD servers in an enterprise;

receiving from the plurality of network elements information indicative of changes to network attributes selected from the group consisting of AD domains, additions and subtractions of AD servers and changes in an IP address of AD servers;

transmitting the received AD domains and AD servers to a tenant administrator and requesting credentials to communicate with added AD servers using Windows Management Instrumentation (WMI);

executing an algorithm to determine which element will contact specific AD instances in order to contain WMI communication over LAN and minimize WMI communication over WAN;

monitoring, using the WMI role on the network elements, the AD servers security login events comprising an IP address, a user AD ID and a user name;

converting the login events to IP-to-user events and transmitting these to the ISM service in the controller;

using the ISM service to map these IP-to-user events to the right spoke site to produce a plurality of enriched IP-to-user events;

sending the events with enriched information comprising one or more group IDs for the user to the element in the spoke site; and

using the enriched IP-to-user events at the spoke site to enforce policy based on user and group IDs and to enrich flow and application statistics with user and group information.

16. The method of claim 15 further employing a multi-tenant controller based mapping of a user or device identity to a network level identity.

17. The method of claim 15 further comprising performing application analysis on a per session basis.

18. The method of claim 15 further comprising routing traffic based, at least in part, on a dynamic and automated QoS definition.

19. The method of claim 18 further comprising employing on the traffic modeling and analytics selected from the group consisting of Pareto and Weibull.

20. The method of claim 19 further comprising employing QoS standardized controls selected from the group consisting of shaping, policing, random early discard, tail drop, low latency queues, fair queues, anomaly queues and buffers.