Managing cloud service with community invitations

• US 9,071,606 B2
• Filed: 03/13/2013
• Issued: 06/30/2015
• Est. Priority Date: 03/13/2013
• Status: Active Grant

• Current Assignee: MEETRIX COMMUNICATIONS, INC.
• Original Assignee: MEETRIX COMMUNICATIONS, INC.
• Inventors: Braun, James, Dykstra, Jebb
• Primary Examiner(s): Chea, Philip
• Assistant Examiner(s): Chen, Wuji
• Application Number:
  US13/802,180
• Publication Number:
  US 20140280932A1
• Time in Patent Office: 839 Days
• Field of Search: 709/225
• US Class Current: 1/1
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/104 Grouping of entities

Abstract

An illustrative system for managing a plurality of cloud services that includes a first cloud service, a second cloud service, a relational database, a cloud management console, a global user profile, an invitation, and a synchronization module. Each cloud service includes an LDAP directory configured to manage end users accessing the corresponding cloud service. The relational database is communicatively coupled to each LDAP directory. The cloud management console manages the relational database, which identifies a maximum number of end users that can access each cloud service and an end date for accessing each cloud service. The global user profile is stored on the relational database. The invitation communicated from the cloud management console enables an end user to access the cloud service. The synchronization module enables the relational database to synchronize with each of the LDAP directories according to each end user'"'"'s accepted invitations.

Claims

1. A system for managing on-boarding a plurality of cloud services, the system comprising:

at least one first hardware processor associated with a first cloud service including a first LDAP (Lightweight Directory Access Protocol) directory configured to manage end users'"'"' accessing the first cloud service;

a first per seat license to the first cloud service that includes a first upper limit of end users that can access the first cloud service and a first end date for the first per seat license;

at least one second hardware processor associated with a second cloud service including a second LDAP directory configured to manage users'"'"' access the second cloud service;

a second per seat license to the second cloud service that includes a second upper limit of end users that can access the second cloud service and a second end date for the second per seat license;

a cloud management console communicatively coupled to the first LDAP directory and the second LDAP directory, wherein the cloud management console communicates a plurality of invitations to access at least one of the first cloud service and the second cloud service;

at least one third hardware processor associated with a cloud database module associated with the cloud management console, the cloud database module receives a plurality of global user profiles, stores the communicated invitations, and stores the accepted invitations;

the global user profile includes a plurality of data fields that are communicated to at least one of the first cloud service and the second cloud service;

wherein acceptance of the invitation provides access to at least one of the first cloud service and the second cloud service; and

a synchronization module associated with the cloud management console that enables the cloud database module to synchronize with each of the LDAP directories according to the accepted invitations for at least one of the first per seat license and the second per seat license so that the first upper limit of the first per seat licenses and the second upper limit of the second per seat licenses is not exceeded.

2. The system for managing on-boarding cloud services of claim 1 further comprising an Organizational Unit that is established by the Administrator, wherein the Organizational Unit includes a plurality of end users that have permission to access at least one of the first cloud service and the second cloud service.

3. The system for managing on-boarding cloud services of claim 2, wherein the cloud management console enables the Administrator to control the database and the Organizational Unit so that the Administrator can communicate a plurality of invitations to the Organizational Unit.

4. The system for managing on-boarding cloud services of claim 1 further comprising,

a first-tier Administrator that identifies a community and an upper limit of users that can belong to the community;

and

a second-tier Administrator that is selected by the first-tier Administrator, wherein the second-tier Administrator is capable of creating at least one Organizational Unit that is a subset of the end users within the community.

5. The system for managing on-boarding cloud services of claim 4 wherein the second-tier Administrator communicates the invitation to each member of the Organizational Unit.

6. The system for managing on-boarding cloud services of claim 1 wherein the accepted invitation triggers communicating the global user profile data fields stored on the database to at least one of the first LDAP directory and the second LDAP directory.

7. The system for managing on-boarding cloud services of claim 1 further comprising enabling the Administrator to remove an end user from the community, when the end user does not accept the invitation communicated from the Administrator to the end user.

8. A system for managing on-boarding a plurality of cloud services, the system comprising:

a first memory that stores a first cloud service including a first LDAP directory configured to manage end users accessing the first cloud service;

a second memory that stores a second cloud service including a second LDAP directory configured to manage users access the second cloud service;

a third memory associates with a relational database that is configured to be communicatively coupled to the first LDAP directory for the first cloud service and the second LDAP directory for the second cloud service, wherein the relational database memory stores a plurality of communicated invitations and a plurality of accepted invitations;

a cloud management console that manages the relational database, which identifies a maximum number of end users that can access each cloud service and an end date for accessing each cloud service, the cloud management console configured to communicate the plurality of invitations to access at least one of the first cloud service and the second cloud service;

a global user profile stored on the relational database, wherein the global user profile includes a plurality of data fields configured to be communicated to at least one of the first cloud service and the second cloud service;

wherein acceptance of the invitation provides access to at least one of the first cloud service and the second cloud service;

a synchronization module associated with the cloud management console that enables the relational database to synchronize with each of the LDAP directories according to the accepted invitations for at least one of a first per seat license and a second per seat license so that the first upper limit of the first per seat licenses and the second upper limit of the second per seat licenses is not exceeded.

9. The system for managing on-boarding cloud services of claim 8 further comprising an Organizational Unit that is established by an Administrator, wherein the Organizational Unit includes a plurality of end users that have permission to access at least one of the first cloud service and the second cloud service.

10. The system for managing on-boarding cloud services of claim 9, wherein the cloud management console enables the Administrator to control the relational database and the Organizational Unit so that the Administrator can communicate a plurality of invitations to the Organizational Unit.

11. The system for managing on-boarding cloud services of claim 8 further comprising,

a first-tier Administrator that identifies a community and an upper limit of users that can belong to the community;

and

a second-tier Administrator that is selected by the first-tier Administrator, wherein the second-tier Administrator is capable of creating at least one Organizational Unit that is a subset of the end users within the community.

12. The system for managing on-boarding cloud services of claim 11 wherein the second-tier Administrator communicates the invitation to each member of the Organizational Unit.

13. The system for managing on-boarding cloud services of claim 8 wherein the accepted invitation triggers communicating the global user profile data fields stored on the database to at least one of the first LDAP directory and the second LDAP directory.

14. The system for managing on-boarding cloud services of claim 8 further comprising enabling the Administrator to remove an end user from the community, when the end user does not accept the invitation communicated from the Administrator to the end user.

15. A method for managing on-boarding a plurality of cloud services, the method comprising:

communicating a plurality of invitations from a cloud management console, wherein the invitation is configured to receive a user input that enables an end user to access at least one of a first cloud service and a second cloud service;

managing access to a first memory that stores the first cloud service with a first LDAP directory that is associated with the first cloud service;

managing access to a second memory that stores the second cloud service with a second LDAP directory that is associated with the second cloud service;

enabling a third memory associated with a relational database to be communicatively coupled to the first LDAP directory for the first cloud service and the second LDAP directory for the second cloud service, wherein the relational database is associated with the cloud management module;

controlling the relational database from the cloud management console, which identifies a maximum number of end users that can access each cloud service and an end date for accessing each cloud service;

enabling the cloud management module to receive a plurality of accepted invitations, in which each accepted invitation provides access to at least one of the first cloud service and the second cloud service;

storing a global user profile on the relational database, wherein the global user profile includes a plurality of data fields configured to be communicated to at least one of the first cloud service and the second cloud service;

synchronizing the relational database with each of the LDAP directories with a synchronization module associated with the cloud management module, the synchronization module enables the relational database to synchronize with each of the LDAP directories according to the accepted invitations for at least one of the first per seat licenses and the second per seat licenses so that the upper limit of the first seat licenses and the second upper limit of the second per seat licenses is not exceeded.

16. The method of managing on-boarding cloud services of claim 15 further comprising establishing an Organizational Unit that includes a plurality of end users that have permission to access at least one of the first cloud service and the second cloud service, wherein the Organizational Unit is set up by an Administrator.

17. The method of managing on-boarding cloud services of claim 16 wherein the cloud management console enables the Administrator to control the relational database and the Organizational Unit so the Administrator can communicate a plurality of invitations to the Organizational Unit.

18. The method of managing on-boarding cloud services of claim 15 further comprising,

enabling a first-tier Administrator to identify a community and an upper limit of users that can belong to the community;

and

selecting a second-tier Administrator that is capable of creating at least one Organizational Unit that is a subset of the end users within the community.

19. The method of managing on-boarding cloud services of claim 18 wherein the second-tier Administrator communicates the invitations to the Organizational Unit.

20. The method of managing on-boarding cloud services of claim 15 further comprising communicating the global user profile data fields stored on the database to at least one of the first LDAP directory and the second LDAP directory, when the invitation is accepted by the end user.