×

Multi-tenancy using suite of authorization manager components

  • US 8,271,536 B2
  • Filed: 11/14/2008
  • Issued: 09/18/2012
  • Est. Priority Date: 11/14/2008
  • Status: Active Grant
First Claim
Patent Images

1. A method, implemented at a server computer system in a computer networking environment that includes plurality of computing systems, the method for implementing a multi-tenancy service component configured to provide multi-tenancy capabilities to submitted services that do not otherwise provide multi-tenancy capabilities, the method comprising:

  • an act of instantiating a hosting service that includes a multi-tenancy component that is configurable to define how the hosting service provides resource access to one or more resources of a submitted service including enabling a single instance of the one or more resources to be accessed by a plurality of users such that the submitted service functions as a multi-tenancy service even though the submitted service does not by itself provide multi-tenancy capabilities;

    an act of receiving the submitted service submitted to be hosted by the hosting service, the submitted service including a portion of use information that defines that access to a single instance of the one or more resources of the submitted service is to be provided to a plurality of users;

    an act of configuring the multi-tenancy component to provide access to the single instance of the one or more resources of the submitted service to the plurality of users by configuring a validation plug-in that defines one or more resource instance claims for each of the plurality of users that define the type of access each of the plurality of users will have to the single instance of the one or more resources, wherein the plug-in provides an application programming interface for creating, updating and deleting resource instance claims in an authentication database;

    an act of receiving a security token from a first of the plurality of users, the security token including one or more resource instance claims that identify the first user'"'"'s purported access rights to the single instance of the one or more resources;

    an act of validating the security token received from the first user, including validating the one or more resource instance claims in the security token by comparing the one or more resource instance claims in the security token to resource instance claims in the authentication database to verify that the one or more resource instance claims in the security token are included in the authentication database;

    an act of providing, to the first user, access to the single instance of the one or more resources in accordance with the validated one or more resource instance claims;

    an act of receiving a security token from a second of the plurality of users, the security token including one or more resource instance claims that identify the second user'"'"'s purported access rights to the single instance of the one or more resources;

    an act of validating the security token received from the second user, including validating the one or more resource instance claims in the security token by comparing the one or more resource instance claims in the security token to resource instance claims in the authentication database to verify that the one or more resource instance claims in the security token are included in the authentication database; and

    an act of providing, to the second user, access to the single instance of the one or more resources in accordance with the validated one or more resource instance claims.

View all claims
  • 2 Assignments
Timeline View
Assignment View
    ×
    ×