Authorization code management for published static applications

1. A client computer system comprising:

a processor;

a user interface coupled to the processor, the user interface including an input device and a display screen; and

memory coupled to the processor and storing instructions that, when executed by the processor, cause the client computer system to perform operations comprising:

presenting, on the display screen via a web browser, a web page received from a first datacenter associated with a tenant-specific endpoint (TSE) for a software application operating on the client computer system;

receiving, via the input device into the web page presented in the web browser, first authentication information for a user of the client computer system;

transmitting the first authentication information to the first datacenter;

receiving, from the first datacenter, redirection information for a second datacenter associated with a TSE for the user;

redirecting the web browser to the second datacenter based on the redirection information;

receiving, via the input device via the web browser, second authentication information for the user;

transmitting the second authentication information to the second datacenter;

receiving an authentication token from the second datacenter, wherein the authentication token is a self-encoded signed token generated by the TSE associated with the user to allow access by the user to resources on the second datacenter; and

redirecting the web browser based on the received authentication token.

2. The system of claim 1 , wherein the memory further stores instructions for causing the client computer system to perform operations comprising:

presenting, via the display screen of the user interface, a login page including an option to perform an authorization;

receiving, via the input device, a selection of the option to perform the authorization; and

redirecting the web browser to the first datacenter to receive the web page.

3. The system of claim 1 , wherein the first authentication information is a username associated with the user, and the second authentication information is a password associated with the user.

4. The system of claim 1 , wherein the memory further stores instructions for causing the client computer system to perform operations comprising:

subsequent to redirecting the web browser to the second datacenter, presenting a second web page received from second application datacenter; and

receiving the second authentication information via the input device into the second web page.

5. The system of claim 1 , wherein the software application operating on the client computer system is loaded into the web browser prior to presenting the web page from the first datacenter.

6. The system of claim 1 , wherein the redirecting of the web browser to the second datacenter is performed by the software application via an application program interface (API) call to the web browser.

7. A tangible, non-transitory computer-readable medium storing instructions that, when executed by a client computer system, cause the client computer system to perform operations comprising:

presenting, on a display screen coupled to the client computer system and via a web browser, a web page received from a first datacenter associated with a tenant-specific endpoint (TSE) for a software application operating on the client computer system;

receiving, via an input device coupled to the client computer system and into the web page presented in the web browser, first authentication information for a user of the client computer system;

transmitting the first authentication information to the first datacenter;

receiving, from the first datacenter, redirection information for a second datacenter associated with a TSE for the user;

redirecting the web browser to the second datacenter based on the redirection information;

receiving, via the input device via the web browser, second authentication information for the user;

transmitting the second authentication information to the second datacenter;

receiving an authentication token from the second datacenter, wherein the authentication token is a self-encoded signed token generated by the TSE associated with the user to allow access by the user to resources on the second datacenter; and

redirecting the web browser based on the received authentication token.

8. The computer-readable medium of claim 7 , wherein the medium further stores instructions for causing the client computer system to perform operations comprising:

presenting, via the display screen, a login page including an option to perform an authorization;

receiving, via the input device, a selection of the option to perform the authorization; and

redirecting the web browser to the first datacenter to receive the web page.

9. The computer-readable medium of claim 7 , wherein the first authentication information is a username associated with the user, and the second authentication information is a password associated with the user.

10. The computer-readable medium of claim 7 , wherein the medium further stores instructions for causing the client computer system to perform operations comprising:

subsequent to redirecting the web browser to the second datacenter, presenting a second web page received from second application datacenter; and

receiving the second authentication information via the input device into the second web page.

11. The computer-readable medium of claim 7 , wherein the software application operating on the client computer system is loaded into the web browser prior to presenting the web page from the first datacenter.

12. The computer-readable medium of claim 7 , wherein the redirecting of the web browser to the second datacenter is performed by the software application via an application program interface (API) call to the web browser.

13. A method comprising:

presenting, by a client computer system on a display screen coupled to the client computer system and via a web browser, a web page received from a first datacenter associated with a tenant-specific endpoint (TSE) for a software application operating on the client computer system;

receiving, by the client computer system via an input device coupled to the client computer system and into the web page presented in the web browser, first authentication information for a user of the client computer system;

transmitting the first authentication information to the first datacenter;

receiving, by the client computer system from the first datacenter, redirection information for a second datacenter associated with a TSE for the user;

redirecting, by the client computer system, the web browser to the second datacenter based on the redirection information;

receiving, by the client computer system via the input device via the web browser, second authentication information for the user;

transmitting, by the client computer system, the second authentication information to the second datacenter;

receiving, by the client computer system, an authentication token from the second datacenter, wherein the authentication token is a self-encoded signed token generated by the TSE associated with the user to allow access by the user to resources on the second datacenter; and

redirecting, by the client computer system, the web browser based on the received authentication token.

14. The method of claim 13 , further comprising:

presenting, by the client computer system via the display screen, a login page including an option to perform an authorization;

receiving, by the client computer system via the input device, a selection of the option to perform the authorization; and

redirecting, by the client computer system, the web browser to the first datacenter to receive the web page.

15. The method of claim 13 , wherein the first authentication information is a username associated with the user, and the second authentication information is a password associated with the user.

16. The method of claim 13 , further comprising:

subsequent to redirecting the web browser to the second datacenter, presenting a second web page received from second application datacenter; and

receiving the second authentication information via the input device into the second web page.

17. The method of claim 13 , wherein the software application operating on the client computer system is loaded into the web browser prior to presenting the web page from the first datacenter.

18. The method of claim 13 , wherein the redirecting of the web browser to the second datacenter is performed by the software application via an application program interface (API) call to the web browser.