FEDERATED FULL DOMAIN LOGON

• US 20160094543A1
• Filed: 09/30/2015
• Published: 03/31/2016
• Est. Priority Date: 09/30/2014
• Status: Active Grant

• Current Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Original Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Inventors: Innes, Andrew, Mayers, Chris
• Granted Patent: US 10,122,703 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 21/33 using certificates
• CPC Class Codes: H04L 63/061 for key exchange, e.g. in peer-to-peer networks cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838
• CPC Class Codes: H04L 63/0815 providing single-sign-on or federations
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/0853 using an additional device, e.g. smartcard, SIM or a different communication terminal cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234
• CPC Class Codes: H04L 63/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 9/3228 One-time or temporary data, i.e. information which is sent for every authentication or authorization, e.g. one-time-password, one-time-token or one-time-key
• CPC Class Codes: H04L 9/3234 involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853
• CPC Class Codes: H04L 9/3263 involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements network architectures or network communication protocols for supporting authentication of entities using certificates in a packet data network H04L63/0823

Abstract

Methods and systems for faster and more efficient smart card logon and for giving a client device full domain access in a remote computing environment are described herein. Components used to implement fast smart card logon may also be used to implement a federated full domain logon. A virtual smart card credential, which may be ephemeral, may be issued based on the acceptance of an external authentication event. Example external authentication events include logon at a Security Assertion Markup Language (SAML) Identity Provider, smart card authentication over TLS or SSL, and alternative authentication credentials such as biometrics or one-time password (OTP) without AD password. Moreover, the certificate operation interception components from fast smart card logon may be used to enable interaction with the virtual smart card without fully emulating a smart card at the PC/SC API level. The virtual smart card may be created locally at the authentication server or on a separate server that may be highly protected.

Claims

1. A method comprising:

storing a certificate at a credential mapper of a server device;

corresponding, by the server device, a token to the certificate stored at the credential mapper;

receiving, at the server device and from a client device, the token;

determining, at the server device, whether the client device has authenticated with an identity providing device based on the token received from the client device; and

in response to determining that the client device has authenticated with the identity providing device, providing a temporary certificate for granting the client device access to a domain.

2. The method of claim 1, wherein determining whether the client device has authenticated with the identity providing device comprises:

sending, by the server device to the identity providing device, information from the token received from the client device; and

receiving, from the identity providing device, confirmation that the client device has authenticated with the identity providing device.

3. The method of claim 1, wherein determining whether the client device has authenticated with the identity providing device comprises performing one or more of the following:

determining, by the credential mapper of the server device, whether the token received from the client device corresponds to a token issued by the identity providing device;

determining, by a gateway service of the server device, whether the token received from the client device corresponds to the token issued by the identity providing device;

or

determining, by an application store of the server device, whether the token received from the client device corresponds to the token issued by the identity providing device.

4. The method of claim 1, further comprising:

linking the temporary certificate to a proof key at the client device, wherein the providing the temporary certificate comprises providing the temporary certificate in response to a determination that the client device has the proof key.

5. The method of claim 1, further comprising:

prior to providing the temporary certificate, generating the temporary certificate based on the certificate stored at the credential mapper in response to determining that the client device has authenticated with the identity providing device based on the token.

6. The method of claim 1, wherein the temporary certificate comprises a time-limited certificate.

7. The method of claim 1, wherein the temporary certificate comprises a smart card class certificate.

8. An apparatus comprising:

a processor; and

memory storing computer-executable instructions that, when executed by the processor, cause the apparatus to;

store a certificate at a credential mapper of the apparatus;

correspond a token to the certificate stored at the credential mapper;

receive, from a client device, the token;

determine whether the client device has authenticated with an identity providing device based on the token received from the client device; and

in response to determining that the client device has authenticated with the identity providing device, provide a temporary certificate for granting the client device access to a domain.

9. The apparatus of claim 8, wherein determining whether the client device has authenticated with the identity providing device comprises:

send, to the identity providing device, information from the token received from the client device; and

receive, from the identity providing device, confirmation that the client device has authenticated with the identity providing device.

10. The apparatus of claim 8, wherein determining whether the client device has authenticated with the identity providing device comprises performing one or more of the following:

determining, by the credential mapper of the apparatus, whether the token received from the client device corresponds to a token issued by the identity providing device;

determining, by a gateway service of the apparatus, whether the token received from the client device corresponds to the token issued by the identity providing device;

or

determining, by an application store of the server device, whether the token received from the client device corresponds to the token issued by the identity providing device.

11. The apparatus of claim 8, wherein the memory stores computer-executable instructions that, when executed by the processor, cause the apparatus to:

link the temporary certificate to a proof key at the client device, wherein the providing the temporary certificate comprises providing the temporary certificate in response to a determination that the client device has the proof key.

12. The apparatus of claim 8, wherein the memory stores computer-executable instructions that, when executed by the processor, cause the apparatus to:

prior to providing the temporary certificate, generate the temporary certificate based on the certificate stored at the credential mapper in response to determining that the client device has authenticated with the identity providing device based on the token.

13. The apparatus of claim 8, wherein the temporary certificate comprises a time-limited certificate.

14. The apparatus of claim 8, wherein the temporary certificate comprises a smart card class certificate.

15. A method comprising:

sending, by a client device and to an identity providing device, credentials for authenticating the client device with the identity providing device;

receiving, at the client device and from the identity providing device, a token indicating that the client device is authenticated with the identity providing device;

sending, by the client device and to a server device, the token; and

in response to the client device receiving an indication from the server device that the client device has been granted access to a domain based on the token, using a temporary certificate to access the domain.

16. The method of claim 15, wherein the server device uses the token to determine whether the client device is authenticated with the identity providing device.

17. The method of claim 15, wherein the token is linked to a certificate stored at a credential mapper of the server device.

18. The method of claim 17, wherein the temporary certificate is generated based on the certificate stored at the credential mapper.

19. The method of claim 15, wherein the temporary certificate comprises a time-limited certificate.

20. The method of claim 15, wherein the temporary certificate comprises a smart card class certificate.