Abstract: The present disclosure is directed towards systems and methods for using a software as a service (“SaaS”) product. The systems and methods request, in response to receiving a request to purchase a software as a service product, a user identifier. Additionally, in response to receiving the user identifier, the systems and methods enable a completed purchase of the SaaS product with a provisional account associated with the user identifier. Furthermore, the systems and methods prevent use of the software as a service product through the provisional account and, in response to a completed purchase of the software as a service product, request a creation of a user credential. Upon receiving the user credential, the systems and methods convert the provisional account into a permanent account associated with the user identifier and user credential and enable use of the SaaS product through the permanent account.

Abstract: Techniques for invitations for establishing relationships are described. In at least some embodiments, an architecture is implemented which provides simple and integrated ways for establishing relationships between various entities. The architecture includes invitations that can be used to invite users to establish relationships with entities. A user that receives an invitation can interact with the invitation, such as to accept or decline an invitation to establish a relationship with an entity. If a user accepts an invitation, a relationship can be established between the user and an inviting entity. In at least some embodiments, the relationship can enable the user to perform various actions and/or access resources associated with the entity.

Abstract: The present disclosure is directed towards systems and methods for using a software as a service (“SaaS”) product. The systems and methods request, in response to receiving a request to purchase a software as a service product, a user identifier. Additionally, in response to receiving the user identifier, the systems and methods enable a completed purchase of the SaaS product with a provisional account associated with the user identifier. Furthermore, the systems and methods prevent use of the software as a service product through the provisional account and, in response to a completed purchase of the software as a service product, request a creation of a user credential. Upon receiving the user credential, the systems and methods convert the provisional account into a permanent account associated with the user identifier and user credential and enable use of the SaaS product through the permanent account.

Abstract: The present disclosure is directed towards systems and methods for using a software as a service (“SaaS”) product. The systems and methods request, in response to receiving a request to purchase a software as a service product, a user identifier. Additionally, in response to receiving the user identifier, the systems and methods enable a completed purchase of the SaaS product with a provisional account associated with the user identifier. Furthermore, the systems and methods prevent use of the software as a service product through the provisional account and, in response to a completed purchase of the software as a service product, request a creation of a user credential. Upon receiving the user credential, the systems and methods convert the provisional account into a permanent account associated with the user identifier and user credential and enable use of the SaaS product through the permanent account.

Abstract: The present disclosure is directed towards systems and methods for using a software as a service (“SaaS”) product. The systems and methods request, in response to receiving a request to purchase a software as a service product, a user identifier. Additionally, in response to receiving the user identifier, the systems and methods enable a completed purchase of the SaaS product with a provisional account associated with the user identifier. Furthermore, the systems and methods prevent use of the software as a service product through the provisional account and, in response to a completed purchase of the software as a service product, request a creation of a user credential. Upon receiving the user credential, the systems and methods convert the provisional account into a permanent account associated with the user identifier and user credential and enable use of the SaaS product through the permanent account.

Abstract: Systems and methods are disclosed for activating features of software products at a client device utilizing a features set ID embedded in an access token. In particular, in one or more embodiments, the disclosed systems and methods provide a master feature registry to a client device in conjunction with downloading a software product. Moreover, upon authenticating a user of the client device, the disclosed systems and methods generate a feature set ID indicating the software products the user is permitted to access. The disclosed systems and methods embed the generated feature set ID into an access token and send the access token to the client device. The client device can utilize the embedded feature set ID in conjunction with the master feature registry to identify authorized features. Moreover, the client device can activate the authorized features in relation to the software product.

Abstract: Resource feature transfer is described. In one or more embodiments, information is collected about interaction of an unauthenticated user of a computing device with a resource, such as content (e.g., a web page) or an application. The information may identify the user, a device or application used to interact with the resource, and so on. This information is communicated to an identity management service (IMS) to determine features to make accessible to the unauthenticated user when interacting with the resource. During the interaction, the user initiates authentication to a corresponding user profile. To achieve a consistent user experience, the features made accessible to the user when unauthenticated are transferred so they are also accessible when authenticated. To do this, authentication information is communicated to the IMS with a token indicating the features determined for the unauthenticated user. The IMS then merges these features with features indicated by the user profile.

Abstract: Systems and methods are disclosed for activating features of software products at a client device utilizing a features set ID embedded in an access token. In particular, in one or more embodiments, the disclosed systems and methods provide a master feature registry to a client device in conjunction with downloading a software product. Moreover, upon authenticating a user of the client device, the disclosed systems and methods generate a feature set ID indicating the software products the user is permitted to access. The disclosed systems and methods embed the generated feature set ID into an access token and send the access token to the client device. The client device can utilize the embedded feature set ID in conjunction with the master feature registry to identify authorized features. Moreover, the client device can activate the authorized features in relation to the software product.

Abstract: Techniques for invitations for establishing relationships are described. In at least some embodiments, an architecture is implemented which provides simple and integrated ways for establishing relationships between various entities. The architecture includes invitations that can be used to invite users to establish relationships with entities. A user that receives an invitation can interact with the invitation, such as to accept or decline an invitation to establish a relationship with an entity. If a user accepts an invitation, a relationship can be established between the user and an inviting entity. In at least some embodiments, the relationship can enable the user to perform various actions and/or access resources associated with the entity.

Abstract: Resource feature transfer is described. In one or more embodiments, information is collected about interaction of an unauthenticated user of a computing device with a resource, such as content (e.g., a web page) or an application. The information may identify the user, a device or application used to interact with the resource, and so on. This information is communicated to an identity management service (IMS) to determine features to make accessible to the unauthenticated user when interacting with the resource. During the interaction, the user initiates authentication to a corresponding user profile. To achieve a consistent user experience, the features made accessible to the user when unauthenticated are transferred so they are also accessible when authenticated. To do this, authentication information is communicated to the IMS with a token indicating the features determined for the unauthenticated user. The IMS then merges these features with features indicated by the user profile.

Abstract: Techniques for invitations for establishing relationships are described. In at least some embodiments, an architecture is implemented which provides simple and integrated ways for establishing relationships between various entities. The architecture includes invitations that can be used to invite users to establish relationships with entities. A user that receives an invitation can interact with the invitation, such as to accept or decline an invitation to establish a relationship with an entity. If a user accepts an invitation, a relationship can be established between the user and an inviting entity. In at least some embodiments, the relationship can enable the user to perform various actions and/or access resources associated with the entity.

Abstract: Providers of Internet based services must handle requests from many different customers. However, to make the experience simple and effective, a system for allowing a user to enter a simple Uniform Resource Locator based upon the user's identifier is provided that re-directs the user to a server cluster allocated to that user. The system is capable of periodic load re-balancing and can handle many different types of services for each user.

Abstract: Various techniques for providing a device token protocol for authorization and persistent authentication shared across applications are disclosed. In some embodiments, a device token protocol for authorization and persistent authentication shared across applications includes sending user credentials to a remote server to authenticate a user on a device for a plurality of applications; and receiving a device token from the remote server for the user to authenticate the user for the plurality of applications on the device, in which the device token facilitates authentication and authorization.

Abstract: Techniques for invitations for establishing relationships are described. In at least some embodiments, an architecture is implemented which provides simple and integrated ways for establishing relationships between various entities. The architecture includes invitations that can be used to invite users to establish relationships with entities. A user that receives an invitation can interact with the invitation, such as to accept or decline an invitation to establish a relationship with an entity. If a user accepts an invitation, a relationship can be established between the user and an inviting entity. In at least some embodiments, the relationship can enable the user to perform various actions and/or access resources associated with the entity.

Abstract: Various techniques for providing a device token protocol for authorization and persistent authentication shared across applications are disclosed. In some embodiments, a device token protocol for authorization and persistent authentication shared across applications includes sending user credentials to a remote server to authenticate a user on a device for a plurality of applications; and receiving a device token from the remote server for the user to authenticate the user for the plurality of applications on the device, in which the device token facilitates authentication and authorization.

Abstract: Providers of Internet based services must handle requests from many different customers. However, to make the experience simple and effective, a system for allowing a user to enter a simple Uniform Resource Locator based upon the user's identifier is provided that re-directs the user to a server cluster allocated to that user. The system is capable of periodic load re-balancing and can handle many different types of services for each user.