Inter-application management of user credential data
A system and apparatus for enhancing the functionality and utility of an authentication process for web applications is disclosed.
1. A method, comprising:
providing, with a hardware computing device, at least one of two security framework configurations, wherein a first configuration utilizes a cookie and a second configuration utilizes server-side storage;
performing user authorization, with the hardware computing device, using at least one of the two security framework configurations, wherein performing the user authorization with the server-side storage includes storing developer-defined user information (DDUI) in a shared session cache;
wherein either the user is recognized because a cookie or a session context containing a security token was provided, or the user is not recognized and diverted to a security handshake, or a token request is utilized to obtain a session identifier, API endpoint and authentication token;
wherein when using the server-side storage, the hardware computing device is configured to not write locally to an application memory, but instead to access a shared session cache, where each of a plurality of servers are to be given access to a specific session cache; and
wherein performing the user authorization is done through a client web application executed by a hardware computing device to allow access to an on-demand database service.
2. The method of claim 1 , wherein a security framework to provide the at least one of two security framework configurations comprises a plurality of generic servlet filters and spring security filters.
3. The method of claim 1 , further comprising a generic servlet filter performs OAuth flow and routes the user to the login page.
4. The method of claim 3 , wherein the generic servlet filter is used within servlet-based web applications that operate without using any specific security framework.
5. The method of claim 1 , further comprising:
facilitating a choice between storing user data in browser cookies or server side sessions, thereby resulting in application instances being completely stateless.
6. A multi-tenant database system, comprising:
a group of hardware computing devices providing a database system to store data for each of multiple tenants;
an application server communicably coupled to the database system and to a network, the application server to provide at least one of two security framework configurations, wherein a first configuration utilizes a cookie and a second configuration utilizes server-side storage, to perform user authorization using at least one of the two security framework configurations, wherein performing the user authorization with the server-side storage includes storing developer-defined user information (DDUI) in a shared session cache, wherein either the user is recognized because a cookie or a session context containing a security token was provided, or the user is not recognized and diverted to a security handshake, or a token request is utilized to obtain a session identifier, API endpoint and authentication token, wherein when using the server-side storage, the hardware computing device is configured to not write locally to an application memory, but instead to access a shared session cache, where each of a plurality of servers are to be given access to a specific session cache, and wherein performing the user authorization is done through a client web application executed by a hardware computing device to allow access to an on-demand database service.
7. The multi-tenant database system of claim 6 , wherein a security framework to provide the at least one of two security framework configurations comprises a plurality of generic servlet filters and spring security filters.
8. The multi-tenant database system of claim 6 , further comprising a generic servlet filter performs OAuth flow and routes the user to the login page.
9. The multi-tenant database system of claim 8 , wherein the generic servlet filter is used within servlet-based web applications that operate without using any specific security framework.
10. The multi-tenant database system of claim 6 , further comprising:
facilitating a choice between storing user data in browser cookies or server side sessions, thereby resulting in application instances being completely stateless.
11. A non-transitory machine-readable medium carrying one or more sequences of instructions for implementing a method for providing an interface for object relationships, comprising:
performing user authorization, with the hardware computing device, using at least one of the two security framework configurations, wherein performing the user authorization with the server-side storage includes storing developer-defined user information (DDUI) in a shared session cache;
wherein either the user is recognized because a cookie or a session context containing a security token was provided, or the user is not recognized and diverted to a security handshake, or a token request is utilized to obtain a session identifier, API endpoint and authentication token;
wherein when using the server-side storage, the hardware computing device is configured to not write locally to an application memory, but instead to access a shared session cache, where each of a plurality of servers are to be given access to a specific session cache; and
wherein performing the user authorization is done through a client web application executed by a hardware computing device to allow access to an on-demand database service.
12. The non-transitory machine-readable medium of claim 11 , wherein a security framework to provide the at least one of two security framework configurations comprises a plurality of generic servlet filters and spring security filters.
13. The non-transitory machine-readable medium of claim 11 , wherein a generic servlet filter performs OAuth flow and routes the user to the login page.
14. The non-transitory machine-readable medium of claim 13 , wherein the generic servlet filter is used within servlet-based web applications that operate without using any specific security framework.
15. The method of claim 11 , further comprising: facilitating a choice between storing user data in browser cookies or server side sessions, thereby resulting in application instances being completely stateless.