Using client certificates to communicate trusted information
A device comprises: a receiver configured to receive a client certificate; a processor coupled to the receiver and configured to: authenticate the client certificate, extract, in response to the authentication, attributes from the client certificate, and create, in response to the extraction, a message comprising reformatted attributes based on the attributes, wherein the reformatted attributes can be trusted; and a transmitter coupled to the processor and configured to transmit the message. A device comprises: a processor configured to: process a client certificate comprising a certificate identifier (ID) attribute, a tenant ID attribute, and a role ID attribute, and package the client certificate in a request for a shared service; and a transmitter coupled to the processor and configured to transmit the request.
1. A gateway server device comprising:
a receiver configured to receive a client certificate from a client; and
a processor coupled to the receiver and configured to:
authenticate the client certificate,
extract, in response to the authentication, attributes from the client certificate, and
create, in response to the extraction, a message comprising reformatted attributes based on the attributes, wherein the reformatted attributes comprise a certificate identifier (ID) attribute, a tenant ID attribute, and a role ID attribute, wherein the certificate ID attribute uniquely identifies the client certificate, wherein the tenant ID attribute specifies which partner data is client accessible, wherein role ID attribute helps to implement role-based access control, and wherein the reformatted attributes can be trusted.
2. The device of claim 1 , wherein the processor is configured to authenticate the client certificate when the client certificate is signed by a private certificate authority associated with the gateway server.
3. The device of claim 1 , wherein the certificate ID identifies the client.
4. The device of claim 1 , wherein the reformatted attributes can be trusted because of the authentication.
5. The device of claim 1 , wherein the reformatted attributes can be trusted because the processor created the message comprising the reformatted attributes.
6. The device of claim 1 , wherein the reformatted attributes are included in Hypertext Transfer Protocol (HTTP) or HTTP Secure (HTTPS) headers.
7. The device of claim 1 , wherein the message is in an Extensible Markup Language (XML) or JavaScript Object Notation (JSON) format.
8. A method comprising:
receiving a client certificate;
authenticating the client certificate based on a signature in the client certificate;
authorizing, in response to the authenticating, access to a shareable service;
extracting, in response to the authenticating, attributes from the client certificate;
creating, in response to the extracting, a message comprising reformatted attributes based on the attributes, wherein the reformatted attributes comprise a certificate identifier (ID) attribute, a tenant ID attribute, and a role ID attribute, wherein the reformatted attributes can be trusted based on the authentication;
transmitting the message;
receiving, in response to the transmitting, a resource associated with the shareable service; and
forwarding the resource.
9. The method of claim 8 , wherein the reformatted attributes are globally unique identifiers (GUIDs) that are unique and cannot be forged, and wherein the certificate ID attribute uniquely identifies the device, the tenant ID attribute specifies which partner data is device accessible, and the role ID attribute specifies a role that the device has while accessing the application server.
10. A method comprising:
receiving a client certificate;
authenticating the client certificate based on a signature in the client certificate;
authorizing, in response to the authenticating, access to a shareable service;
extracting, in response to the authenticating, attributes from the client certificate; and
creating, in response to the extracting, a message comprising reformatted attributes based on the attributes, wherein the reformatted attributes comprise a certificate identifier (ID) attribute, a tenant ID attribute, and a role ID attribute, wherein the reformatted attributes can be trusted based on the authentication and wherein the reformatted attributes are globally unique identifiers (GUIDs) that are unique and cannot be forged, and wherein the certificate ID attribute uniquely identifies the device, the tenant ID attribute specifies which partner data is device accessible, and the role ID attribute specifies a role that the device has while accessing the application server.
11. The method of claim 10 , further comprising transmitting the message.
12. The method of claim 11 , further comprising receiving, in response to the transmitting, a resource associated with the shareable service.
13. The method of claim 12 , further comprising forwarding the resource.