Federated authentication

1. A method comprising:

receiving, at a site, a first message for federated authentication from a browser hosted on a user device;

sending, from the site, a redirect universal resource locator of a partner system to the browser;

receiving a response from the partner system via the browser, the response including a second message that includes an encrypted partner account number (PCN) associated with the partner system that indicates whether an authentication of a user of a first device, at the partner system, was successful;

decrypting the PCN;

determining, based on the decrypted PCN, whether the authentication was successful; and

registering the first device when it is determined that the authentication was successful.

2. The method of claim 1 , wherein the registering the first device includes:

receiving, from the user device, an activation code that identifies the first device; and

issuing a registration token to the user device when it is determined that the authentication was successful based on the second message.

3. The method of claim 2 , further comprising:

receiving, from the first device, a request for a license key for particular content;

determining whether the first device is registered;

determining whether the user is entitled to play the particular content at the first device; and

issuing the license key to the first device when it is determined that the user is entitled to play the particular content at the first device.

4. The method of claim 3 , wherein the first device is the user device.

5. The method of claim 3 , wherein determining whether the first device is entitled to play the particular content includes:

determining whether a total number of sessions associated with the user exceeds a predetermined number;

determining whether the user has a right to have the content streamed to the first device;

determining whether the first device is within a blackout region associated with the particular content; or

determining whether the user has a right to play the content, at the first device, at a particular quality level.

6. The method of claim 1 , further comprising:

receiving a client application identifier from the first device;

validating the client application identifier; and

sending an activation code and the universal resource locator to the first device if the client application identifier is valid.

7. The method of claim 1 , wherein sending the redirect universal resource locator includes:

sending a Security Assertion Markup Language (SAML) request.

8. The method of claim 1 , wherein receiving the response includes:

receiving an extensible hypertext markup language (XHTML) message.

9. The method of claim 8 , wherein the XHTML message includes:

a Security Assertion Markup Language (SAML) response.

10. The method of claim 9 , wherein the SAML response includes the PCN.

11. The method of claim 10 , wherein determining whether the authentication was successful includes:

decrypting the encrypted PCN via a private key associated with the partner system; and

comparing the decrypted PCN to a PCN of the partner system.

12. One or more devices comprising:

one or more network interfaces to:

communicate, over a network, with a user device that is associated with a user;

one or more memories that store instructions to be executed by one or more processors; and

the one or more processors configured to execute the instructions to:

receive, at a site, via the one or more network interfaces, a first message for authentication from a browser hosted on the user device;

send, from the site via the one or more network interfaces, a redirect universal resource locator (URL) to a partner system, to the browser;

receive a response from the partner system via the browser and the one or more network interfaces, the response including a second message that includes an encrypted partner account number (PCN) associated with the partner system that indicates whether an authentication of the user of the user device at the partner system, was successful;

decrypt the PCN;

determine, based on the decrypted PCN, whether the authentication was successful; and

register the user device when the one or more processors determine that the authentication was successful.

13. The one or more devices of claim 12 , wherein when the one or more processors register the user device, the one or more processors are further configured to execute the instructions to:

receive, from the user device, an activation code that identifies the user device;

issue a registration token to the user device when it is determined that the authentication was successful based on the second message; and

store the registration token in the user device.

14. The one or more devices of claim 13 , wherein the one or more devices are further configured to:

receive a request for a license key for particular content from the user device via the one or more network interfaces;

determine whether the user device is registered based on the request;

determine whether the user is entitled to play the particular content at the user device; and

issue the license key to the user device when the one or more processors determine that the user is entitled to play the particular content at the user device.

15. The one or more devices of claim 14 , wherein when the one or more processors determine whether the user device is entitled to play the particular content, the one or more processors are further configured to execute the instructions to at least one of:

determine whether a total number of sessions associated with the user exceeds a predetermined number;

determine whether the user has a right to have the content streamed to the user device;

determining whether the user device is within a blackout region associated with the particular content; or

determine whether the user has a right to play the content, at the user device, at a particular quality level.

16. The one or more devices of claim 12 , wherein the one or more processors are further configured to execute the instructions to:

receive a client application identifier from the user device;

validate the client application identifier; and

send an activation code and the universal resource locator to the user device if the client application identifier is valid.

17. The one or more devices of claim 12 , wherein the redirect URL includes:

a Security Assertion Markup Language request for authentication by the partner system.

18. The one or more devices of claim 12 , wherein the response includes:

an extensible hypertext markup language (XHTML) message.

19. The one or more devices of claim 18 , wherein the XHTML message includes:

a Security Assertion Markup Language (SAML) response.

20. The one or more devices of claim 19 , wherein the SAML response includes the PCN,

wherein when the one or more processors determine whether the authentication was successful, the one or more processors are further configured to execute the instructions to:

decrypt the encrypted PCN via a private key associated with the partner system; and

compare the decrypted PCN to a PCN of the partner system.

21. A device comprising:

a network interface to communicate with a remote system;

a memory that stores instructions; and

one or more processors configured to execute the instructions in the memory to:

send, to a site, via the network interface, a first message for authentication;

receive, from the site via the network interface, a redirect universal resource locator to a partner system;

forward, to the remote system, a response from the partner system via the network interface, the response including a second message that includes an encrypted partner account number (PCN) associated with the partner system that indicates whether an authentication of a user of a first device, at the partner system, was successful;

decrypt the PCN;

send an activation code for the first device to the remote system that accepts the activation code when the remote system determines, based on the decrypted PCN, that the authentication of the user of the first device at the partner system was successful; and

receive a registration token from the remote system via the network interface, wherein the remote system generates the registration token based on the activation code.