Identity management and authentication system for resource access
A system that authorizes access to a resource by a client validates the client and generates a Security Assertion Markup Language (“SAML”) assertion for the valid client. The system then sends an access request with the SAML assertion to a OAuth server. In response, the OAuth server returns an access token for the resource to the client.
1. A non-transitory computer-readable medium having instructions stored thereon that, when executed by a processor, cause the processor to authorize access to a resource by a client, the authorizing comprising:
in response to receiving a single sign-on comprising a password, validating the client;
receiving a request for a Security Assertion Markup Language (SAML) assertion at a Java servlet;
generating the SAML assertion for the valid client;
sending a Hypertext Transfer Protocol (HTTP) access request with the SAML assertion to an Open Authorization (OAuth) server, wherein the sending comprises transmitting an apply access token request from an Enterprise JavaBeans (EJB) stub to an EJB skeleton, wherein the EJB skeleton is adapted to issue access tokens or reload configurations;
receiving at the Java servlet, in response to the sending, an access token for the resource from the OAuth server; and
sending the access token to the client, wherein the access token enables the client to access the resource.
2. The non-transitory computer-readable medium of claim 1 , wherein the Java servlet is packaged in a Web application Archive (WAR) file.
3. The non-transitory computer-readable medium of claim 1 , wherein the access request comprises an identity of the client and an identity of the resource.
4. The non-transitory computer-readable medium of claim 1 , further comprising an SAML MBean that manages an identity provider's certificate.
5. The non-transitory computer-readable medium of claim 1 , further comprising synchronizing metadata associated with the client with the OAuth server.
6. The non-transitory computer-readable medium of claim 1 , further comprising receiving configuration updates from a Java Message Service (JMS) publisher that is in communication with a JMS listener.
7. The non-transitory computer-readable medium of claim 1 , wherein the validating the client comprises at least one of signature validation, checking assertion conditions or checking an assertion subject.
8. A computer implemented method of authorizing access to a resource by a client, the method comprising:
in response to receiving a single sign-on comprising a password, validating the client;
receiving a request for a Security Assertion Markup Language (SAML) assertion at a Java servlet;
generating the SAML assertion for the valid client;
sending a Hypertext Transfer Protocol (HTTP) access request with the SAML assertion to an Open Authorization (OAuth) server, wherein the sending comprises transmitting an apply access token request from an Enterprise JavaBeans (EJB) stub to an EJB skeleton, wherein the EJB skeleton is adapted to issue access tokens or reload configurations;
receiving at the Java servlet, in response to the sending, an access token for the resource from the OAuth server; and
sending the access token to the client, wherein the access token enables the client to access the resource.
9. The method of claim 8 , wherein the Java servlet is packaged in a Web application Archive (WAR) file.
10. The method of claim 8 , wherein the access request comprises an identity of the client and an identity of the resource.
11. The method of claim 8 , further comprising an SAML MBean that manages an identity provider's certificate.
12. The method of claim 8 , further comprising synchronizing metadata associated with the client with the OAuth server.
13. The method of claim 8 , further comprising receiving configuration updates from a Java Message Service (JMS) publisher that is in communication with a JMS listener.
14. The method of claim 8 , wherein the validating the client comprises at least one of signature validation, checking assertion conditions or checking an assertion subject.
15. A web server comprising:
a processor;
instructions stored on a memory device coupled to the processor that, when executed by the processor generate an authorization servlet that, in response to a request to access a resource by a client,
validates the client in response to receiving a single sign-on comprising a password;
receives a request for a Security Assertion Markup Language (SAML) assertion at a Java servlet;
generates the SAML assertion for the valid client;
sends a Hypertext Transfer Protocol (HTTP) access request with the SAML assertion to an Open Authorization (OAuth) server, wherein the sending comprises transmitting an apply access token request from an Enterprise JavaBeans (EJB) stub to an EJB skeleton, wherein the EJB skeleton is adapted to issue access tokens or reload configurations;
receives at the Java servlet, in response to the sending, an access token for the resource from the OAuth server; and
sends the access token to the client, wherein the access token enables the client to access the resource.
16. The web server of claim 15 , further comprising synchronizing metadata associated with the client with the OAuth server.
17. The web server of claim 15 , wherein the instructions, when executed by the processor, further receives configuration updates from a Java Message Service (JMS) publisher that is in communication with a JMS listener.
18. The web server of claim 15 , further comprising an SAML MBean that manages an identity provider's certificate.
19. The web server of claim 15 , wherein the access request comprises an identity of the client and an identity of the resource.
20. The web server of claim 15 , wherein the validating the client comprises at least one of signature validation, checking assertion conditions or checking an assertion subject.