Systems and methods for facilitating seamless authentication of application development platforms
Various embodiments concern mechanisms for facilitating communication between network-accessible platforms for developing, hosting, or running hybrid applications that utilize resources hosted across multiple platforms. Hybrid applications cause messages or “calls” to be passed between the platforms that must be authenticated. For example, when a call is placed by a Heroku platform to a Force.com platform, the call must be authenticated for security purposes. If Heroku has not already been authenticated when the call is submitted, an authentication process is invoked. An event listener can be used to register details regarding the initial callout task, and then register or “fire” an event when the authentication process is successfully completed. Registration of the initial callout task completely separates the authentication process from the resource being invoked. Requests can be completed without requiring further user input using at least some of the details registered by the event listener.
1. A method comprising:
receiving a Hypertext Transfer Protocol (HTTP) call from an application for a resource hosted by a service accessible to a development platform across a network;
determining that the service is not a registered client of the development platform;
passing information regarding the HTTP call through an authentication process, the information including an identifier that specifies an origin of the HTTP call;
causing an event listener to register an event when the authentication process is successfully completed; and
completing, in response to the event being registered, the HTTP call for the resource.
2. The method of claim 1 , wherein the event listener is programmed in Java.
3. The method of claim 1 , wherein the resource is data hosted by the service or a process to be executed by the service.
4. The method of claim 1 , wherein the information further includes a description of the resource, a username, or any combination thereof.
5. The method of claim 1 , further comprising performing the HTTP call for the resource using the information registered by the event listener.
6. The method of claim 1 , wherein the HTTP call is completed responsive to the event being registered without requiring further input from the application.
7. The method of claim 1 , wherein the identifier comprises an organization identifier.
8. The method of claim 1 , wherein the identifier comprises an application identifier.
9. The method of claim 1 , further comprising storing the information regarding the HTTP call in a database.
10. The method of claim 1 , wherein the identifier identifies the application responsible for placing the HTTP call.
11. A system comprising:
at least one processor; and
a memory communicatively coupled with the at least one processor, the memory storing instructions, which when executed by the at least one processor perform a method comprising:
receiving a Hypertext Transfer Protocol (HTTP) call from an application for a resource hosted by a service accessible to a development platform across a network;
determining that the service is not a registered client of the development platform;
passing information regarding the HTTP call through an authentication process, the information including an identifier that specifies from where the HTTP call originated;
causing an event listener to register an event when the authentication process is successfully completed; and
completing, in response to the event being registered, the HTTP call for the resource.
12. The system of claim 11 , wherein the event listener is programmed in Java.
13. The system of claim 11 , wherein the resource is data hosted by the service or a process to be executed by the service.
14. The system of claim 11 , wherein the information further includes a description of the resource, a username, or any combination thereof.
15. The system of claim 11 , wherein the method further comprises performing the HTTP call for the resource using the information registered by the event listener.
16. The system of claim 11 , wherein the HTTP call is completed responsive to the event being registered without requiring further input from the application.
17. The system of claim 11 , wherein the identifier comprises an organization identifier.
18. The system of claim 11 , wherein the identifier comprises an application identifier.
19. The system of claim 11 , wherein the method further comprises storing the information regarding the HTTP call in a database.
20. The system of claim 11 , wherein the identifier identifies the application responsible for placing the HTTP call.