Using client certificates to communicate trusted information
View Patent ↗A trusted information communication device comprising 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.
1. A device comprising:
a receiver configured to receive a client certificate;
a processor comprising hardware or a combination of hardware and software coupled to the receiver and configured via execution of a stored program to:
authenticate the client certificate comprising a role ID attribute,
extract, in response to the authentication, attributes from the client certificate, and
create, in response to the extraction, a message comprising trusted reformatted attributes based on the attributes, wherein the trusted reformatted attributes are trusted because the processor created the message comprising the reformatted attributes, and wherein the trusted reformatted attributes are included in Hypertext Transfer Protocol (HTTP) or HTTP Secure (FITTPS) headers; and
a transmitter coupled to the processor and configured to transmit the message.
2. The device of claim 1 , wherein the device is a gateway server, wherein the receiver is configured to receive the client certificate from a client, and wherein the transmitter is configured to transmit the message to an application server.
3. The device of claim 2 , wherein the processor is configured to authenticate the client certificate when the client certificate is signed by a private certificate authority associated with a gateway server.
4. The device of claim 2 , wherein the trusted reformatted attributes comprise a certificate identifier (ID) attribute that uniquely identifies the client certificate.
5. The device of claim 4 , wherein the certificate ID identifies the client.
6. The device of claim 4 , wherein the trusted reformatted attributes comprise a tenant ID attribute that specifies which client accessible partner data.
7. The device of claim 6 , wherein the role ID attribute helps to implement role-based access control.
8. The device of claim 1 , wherein the trusted reformatted attributes are trusted because of the authentication.
9. The device of claim 1 , wherein the message is in an Extensible Markup Language (XML) or JavaScript Object Notation (JSON) format, and wherein the transmitter is configured to transmit the message using Hypertext Transfer Protocol Secure (HTTPS).
10. A computer system hardware component, wherein the hardware computer system component executes a stored program to perform a method comprising:
receiving, by the computer system hardware component, a client certificate comprising a role ID attribute;
authenticating, by the computer system hardware component, the client certificate based on a signature in the client certificate;
authorizing, by the computer system hardware component, in response to the authenticating, access to a shareable service;
extracting, by the computer system hardware component, in response to the authenticating, attributes from the client certificate; and
creating, by the computer system hardware component, in response to the extracting, a message comprising trusted reformatted attributes based on authentication of the attributes, wherein the computer system hardware component's created trusted reformatted attributes are globally unique identifiers (GUIDs) that are unique and cannot be forged, and wherein the reformatted attributes com rise a certificate identifier (ID) attribute that uniquely identifies the device, a tenant ID attribute that specifies device accessible partner data, and the role ID attribute that specifies a device role while accessing the application server.
11. The computer system hardware component of claim 10 , further comprising:
transmitting, by the computer system hardware component, the message;
receiving, by the computer system hardware component in response to the transmitting, a resource associated with the shareable service; and
forwarding, by the computer system hardware component, the resource.
12. A device comprising:
a receiver configured to receive a client certificate;
a processor comprising hardware or a combination of hardware and software coupled to the receiver and configured via execution of a stored program to:
authenticate the client certificate comprising a role ID attribute,
extract, in response to the authentication, attributes from the client certificate, and
create, in response to the extraction, a message comprising trusted reformatted attributes based on the attributes, wherein the message is in an Extensible Markup Language (XML) or JavaScript Object Notation (JSON) format and wherein the trusted reformatted attributes are trusted because the processor created the message comprising the reformatted; and
a transmitter coupled to the processor and configured to transmit the message and wherein the transmitter is configured to transmit the message using Hypertext Transfer Protocol Secure (HTTPS).
13. The device of claim 12 , wherein the device is a gateway server, wherein the receiver is configured to receive the client certificate from a client, and wherein the transmitter is configured to transmit the message to an application server.
14. The device of claim 13 , wherein the processor is configured to authenticate the client certificate when the client certificate is signed by a private certificate authority associated with a gateway server.
15. The device of claim 13 , wherein the trusted reformatted attributes comprise a certificate identifier (ID) attribute that uniquely identifies the client certificate.
16. The device of claim 15 , wherein the certificate ID identifies the client.
17. The device of claim 15 , wherein the trusted reformatted attributes comprise a tenant ID attribute that specifies which client accessible partner data.
18. The device of claim 17 , wherein the role ID attribute helps to implement role-based access control.
19. The device of claim 12 , wherein the trusted reformatted attributes are trusted because of the authentication.
20. The device of claim 12 , wherein the trusted reformatted attributes are included in Hypertext Transfer Protocol (HTTP) or HTTP Secure (HTTPS) headers.