Configuring Citrix XenDesktop 7.6 and NetScaler Gateway 10.5 with PIV Smart Card Authentication

Transcription

1 Configuring Citrix XenDesktop 7.6 and NetScaler Gateway 10.5 with PIV Smart Card Authentication This guide is intended for those who are deploying smart cards with Citrix products. It provides stepby-step instructions for deployment in United States federal environments. Carel Grove Citrix Authentication Platforms Group

2 Table of Contents Introduction... 1 How this guide is organized... 1 Future editions: What is not in this first edition... 1 Test environment... 2 Objectives... 2 Constraints... 3 Assumptions... 3 Section 1 Configuration Steps (on every machine in the test environment)... 4 Your Organization s Root Certification Authority... 5 Test environment assumptions... 5 Prerequisites... 5 Configuration Steps... 5 Your Organization s Issuing Certificate Authority... 6 Test environment assumptions... 6 Prerequisites... 6 Configuration Steps... 6 Domain Controller Test environment assumptions Prerequisites Configuration Steps User Account Settings Map AD user account to the PIV authentication certificate PKI certificate configuration Virtual Delivery Agent (VDA) Test environment assumptions Prerequisites Configuration Steps Delivery Controller Test environment assumptions Prerequisites Configuration Steps StoreFront Test environment assumptions citrix.com

3 Prerequisites Configuration Steps Configure StoreFront NetScaler Gateway Test Environment assumptions Configuration Steps Hardware security module (HSM) configuration and FIPS key generation Certificate configuration LDAP server configuration NetScaler Gateway virtual server configuration for fed-nsg NetScaler Gateway virtual server configuration for fed-callback Windows 7 (64 bit) Domain-Joined External Endpoint Test environment assumptions Prerequisites Configuration Steps Section 2 Smart Card Single Sign-on Introduction PIN Prompt Origin No reduction (four PIN prompts) Smart card Single Sign-on state A Resultant smart card Single Sign-On behavior A First reduction (three PIN prompts) Smart card Single Sign-on state B (three PIN prompts) Resultant smart card Single Sign-on behavior B Second reduction (two PIN prompts) Smart card Single Sign-on state C (two PIN prompts) Resultant smart card Single Sign-on behavior C Third reduction (one PIN prompt) Smart card Single Sign-on state D (one PIN prompt) Resultant smart card Single Sign-on behavior D Appendices Appendix A: NIST PIV Test Card Certificates, Keys and Chain of Trust Appendix B: Obtaining CA Certificates from Root and Issuing Certificate Authorities citrix.com

4 Appendix C: Manually validate the CA Chain of Trust From a Leaf Certificate to its Corresponding Root Certificate Appendix D: Publishing Certificates to Active Directory Containers Appendix E: Install ActivClient on Windows 7 x Appendix F: How NetScaler Gateway Certificate and LDAP Authentication Policies Map to an Active Directory User Account Last updated 10 April, 2015 Citrix Citrix Systems, Inc. All Rights Reserved citrix.com

5 Introduction This guide describes how to configure a test environment from beginning to end. How this guide is organized The test environment consists of the essential components that constitute a typical Citrix deployment (XenDesktop, Delivery Controller, StoreFront, and virtual desktops accessed via NetScaler Gateway). Each Citrix component is deployed on a dedicated machine. Supporting infrastructure (such as the domain controller and certificate authorities) is also on dedicated machines. The guide describes how to configure each machine, step by step, in chronological order, starting with the root certificate authority and ending with the endpoint. This way, when working on any given configuration step, the reader is assured that all tasks that predicate each configuration step have been completed. There are a few exceptions to this where jumps are necessary. Those are clearly indicated and crossreferenced. Additionally, many notes are included to provide contextual background, and there are also appendices that provide additional in-depth insight. Future editions: What is not in this first edition Topics that are not included in the first edition of the guide: Multi-domain and multi-forest Active Directory environments Non UPN-based smart card certificate to Active Directory account mapping (such as Alternate Security Identity) XenApp coverage Double-hop from the Virtual Delivery Agent to XenApp Additional smart card middleware (only ActivClient is covered in this edition) Additional endpoint coverage (such as Linux, thin clients, Windows 8.1/10, Mac OS X, ios, Android, nondomain-joined Windows, etc.) Information on nonauthentication operations with smart cards (such as S/MIME) PKCS#11 configuration (to use smart cards with browsers such as Firefox) Notes on how CAC and SIPR diverge from PIV, where appropriate citrix.com 1

6 Test environment The test environment can be represented as follows: Browser Domain Controller Root Certificate Authority Issuing Certificate Authority Internet Explorer 11 on Windows 7 SP1 Windows Server 2008 R2 Windows Server 2008 R2 Windows Server 2012 R2 NetScaler Gateway Receiver 10.5 StoreFront Delivery Controller VDA 4.2 on Windows 7 SP1 2.6 on Windows Server 2012 R2 7.6 on Windows Server 2012 R2 7.6 on Windows 7 SP1 Objectives A guide dispensing smart card configuration advice should be: Self-contained: Detailed configuration steps for every product hence step-by-step instructions for installing and configuring products and areas that are not specifically related to smart card authentication, such as installing and configuring the Delivery Controller). Explicitly tested: The documentation itself must be tested. Fool-proof: Cautions against obvious mistakes. It was determined that both military and civilian domains should not be covered in a single document; therefore, CAC cards and SIPR tokens are not discussed. In order to achieve the above objectives, we have to pin down a specific environment. Because there are so many possible variations in a federal environment configuration, a model environment could be tricky to pin down. For example, there could be dozens of different types of endpoints alone. The priority for the first edition was not to cover as many topics or platforms as possible but to ensure that the topics that are covered the essential components of a Citrix deployment are covered in detail and are technically accurate. The topics were researched, and the environment was configured, tested, verified, and finally, documented. When blocking issues were discovered, workarounds were also researched, tested, and documented. citrix.com 2

7 Constraints Some components can be deployed in different ways (or using different methods), depending on the scale of the deployment. For example, the Delivery Controller could use a stand-alone dedicated database server in the case of a large deployment. In a small deployment, SQL Server Express can be installed on the Delivery Controller as part of the Delivery Controller installation to perform the same function. In the test environment, small-scale methods are used. This way, it is complete and self-contained without requiring vast preparation sections. Some notable examples: installing Receiver manually, not using Machine Creation Services (MCS) to provision Virtual Delivery Agents (VDA), not configuring High Availability (HA) on the NetScaler Gateway, and so on. Assumptions The NIST PIV Test Card #1 is the smart card used throughout. Every Windows machine has a server certificate in its personal certificate store, and the machine has access to the associated private key. Active Directory Group Policy settings are configured in the default domain policy. The default domain policy is linked at the domain level. citrix.com 3

8 Section 1 Configuration Steps (on every machine in the test environment) citrix.com 4

9 Your Organization s Root Certification Authority Test environment assumptions Operating system is Windows Server 2008 R2 Prerequisites Active Directory Certificate Services is installed and configured Configuration Steps Export root CA certificate to file To see how this step fits in the overall PKI Configuration process, see the diagram in Appendix D: Publishing Certificates to Active Directory Containers. 1. Open up an instance of the command prompt as an administrator and enter: certutil ca.cert <filename.cer> For example: certutil ca.cert Root_CA_F2-DC-CA.cer This should result in the output as follows: The file Root_CA_F2-DC-CA.cer will appear in the current directory. citrix.com 5

10 Your Organization s Issuing Certificate Authority Test environment assumptions Operating system is Windows Server 2012 R2 The issuing CA trusts the trust root CA IIS is installed and configured IIS port 443 bound to server certificate Active Directory Certificate Services is installed and configured, including web enrollment. Prerequisites The issuing certificate authority server trusts your organization s root certificate authority. In other words, a copy of the root CA certificate for your organization s root certificate authority is located in the issuing certificate authority s Local Computer Trusted Root Certification Authorities store. Configuration Steps Ensure the Key Distribution Center (KDC ) template is available to the issuing certificate authority 1. Start an instance of the Microsoft Management Console (MMC). From the File menu, choose Add/Remove Snap In. From the Available snap-ins list, select Certification Authority, and click Add. The Certification Authority dialog box will appear. Select the local computer as the computer you want the snap-in to manage. Click Finish, and then click OK. 2. Navigate to Certificate Templates: citrix.com 6

11 3. Right-click Certificate Templates. Select New and then Certificate Template to Issue. The Enable Certificate Templates dialog appears: 4. Select the Kerberos Authentication template, and click OK. The Kerberos Authentication template should now be listed under Certificate Templates on your issuing CA. The key purpose of this certificate template is KDC authentication: 5. Restart the CA service. citrix.com 7

12 Submit certificate signing requests (CSR) to your organization s issuing CA NOTE You cannot complete this step until you have generated the CSR files in section Create Certificate Signing Requests (CSR) for each SSL FIPS key of this guide. If you haven t generated the CSR files yet you can skip the rest of this section and continue with configuration of the Domain Controller. Have the CSR files you generated on the NetScaler Gateway device at hand: NOTE You might want to temporarily turn off IE Enhanced Security Configuration in the test environment: Server Manager > Local Server > IE Enhanced Security Configuration. Remember to turn it back on when this step is completed. 6. Start Internet Explorer and point to the following URL: of your Organization s Issuing CA>/certsrv For example: NOTE If the page is not available, you need to ensure that IIS and the appropriate Active Directory Certificate Services (such as Certificate Enrollment Web Service) is installed in server roles on the issuing CA server. 7. If you are prompted for credentials, provide admin credentials. The following page will be displayed: citrix.com 8

13 8. Click Request a Certificate. The following page is displayed: 9. Click Advanced Certificate Request. The following page is displayed: 10. Click Submit a Certificate Request by using a base-64-encoded CMC or PKCS#10 file, or submit a renewal request by using a base-64-encoded PKCS#7 file. The following page is displayed: 11. Use Notepad to open the first CSR file. (In this example, fed-nsg-csr): 12. Select all the text in the file and then copy and paste it into the Base-64-encoded certificate request field in the Saved Request section. citrix.com 9

14 13. Select Web Server in the Certificate Template section. 14. Click Submit. The following is displayed: 15. Click Yes. citrix.com 10

15 16. In the Certificate Issued section, change the encoding format to Base 64 encoded. 17. Click Download Certificate Chain. You will be prompted to open or save the file: 18. Select the drop-down arrow next to Save, and click Save As. It is useful to give the certificate a descriptive name. In this example, the certificate is saved as fed-nsgcert-chain: When the file is opened, it should contain three certificates: 19. Repeat the process for the remaining two CSRs: fed-callback-csr fed-sson-session-csr Before continuing, it is worth inspecting the certificates to ensure that you did not accidently select the wrong template or copy the text for the same CSR more than once: citrix.com 11

16 The Subject CN values are as expected: Public keys are all different: citrix.com 12

17 Certificate Template Name is WebServer for all three: NOTE If you temporarily turned off IE Enhanced Security Configuration in the test environment: Server Manager > Local Server > IE Enhanced Security Configuration, you should turn it back on now. 20. Export the certificates to individual files as follows: Once the files are exported, jump back to section Copy certificate files to NetScaler. citrix.com 13

18 Domain Controller Test environment assumptions Operating system is Windows Server 2008 R2 Prerequisites Enterprise PKI MMC snap-in is installed. The Domain Controller trusts your organization s root and intermediate certificate authorities. In other words, copies of the CA certificates for your organization s root and issuing certificate authorities are located in the Domain Controller s Local Computer Trusted Root Certification Authorities and Intermediate Certification Authorities stores, respectively. Configuration Steps Group policy settings There are a number of group policy settings to configure. The level that you link your group policy settings (local, site, domain, Organizational Unit) depends on your organizational requirements. NOTE The group policy settings will only become active on target machines once the group policy has refreshed. This is governed by the Group Policy Refresh Interval setting. FIPS Mode = On 1. Enable the following policy setting: Policy > Computer Configuration Policies > Windows Settings > Security Settings > Local Policies > Security: System cryptography: Use FIPS compliant algorithms for encryption, hashing and signing Add the Citrix icaclient administrative policy template (ADM) file Citrix provides a Microsoft group policy template file that enables central administration of certain Citrix Receiver configuration settings. Some of the Citrix Receiver settings that can be toggled through the icaclient ADM template govern Single Sign-on/PIN prompt behavior. The icaclient.adm template is copied to the following default location on the endpoint when Citrix Receiver is installed on a 64-bit Windows 7 endpoint: C:\Program Files (x86)\citrix\ica Client\Configuration NOTE Ensure that you are using the icaclient.adm template from the latest version of Citrix Receiver. citrix.com 14

19 Once you ve installed Citrix Receiver on an endpoint in section Install Citrix Receiver, you will be directed back to this section to complete this step. Until then, you can skip ahead to section Import smart card middleware Administrative Policy Template file (ADM) 1. In the group policy mmc-snap-in editor, right-click on Administrative Templates. Select Add/Remove Templates. The Add/Remove Templates dialog will be displayed: 2. Click Add. 3. Select the icaclient.adm file that you copied to the Domain Controller after installing Citrix Receiver in section Group policy ADM. Click Open. The Add/Remove Templates dialog box will be populated as follows: citrix.com 15

20 4. Click Close. 5. Ensure that the Citrix Receiver user authentication settings have been loaded into the Group Policy Editor: citrix.com 16

21 Import smart card middleware Administrative Policy Template file (ADM) Many smart card vendors provide a Microsoft group policy template file that enables central administration of certain middleware configuration settings (for example, some of these middleware settings govern the PIN caching mechanisms in the middleware). For ActivIdentity ActivClient 7.02, the procedure to add the Administrative Template is described in Chapter 2 of the ActivIdentity ActivClient for Windows Administration Guide: Locate the ActivClient.admx template files in the \Admin\Configuration folder on your ActivClient distribution and copy them to C:\Windows\PolicyDefinitions. and Locate the ActivClient.adml template files in the \Admin\Configuration\EN-US folder on your ActivClient distribution and copy them to C:\Windows\PolicyDefinitions\en-US. 1. Start an instance of the Microsoft Management Console. Add the Group Policy Management Editor snap-in. The Group Policy Wizard is spawned. Click Browse to select the Group Policy Object (GPO) to manage. Ensure that the GPO that you select governs the site, domain or OU that contains the machine accounts for computers where ActivClient is (or will be) installed (Windows endpoint and VDA). Click Finish. 2. The ActivClient configuration settings will be accessible from <Name of Policy> Policy > Computer Configuration > Policies > Administrative Templates > ActivIdentity. NOTE The policy deployed using the GPO linked at the site, domain or OU level overrides the same policy if that policy is set locally (for example, manually by a power user on an endpoint). Set PIV to take precedence 1. To prevent a local user or administrator from accidently turning off PIV and turning on CAC, navigate to <Name of Policy> Policy > Computer Configuration > Policies > Administrative Templates > ActivIdentity > ActivClient > Smart Card. Disable Turn on US Department of Defense configuration. If this setting is enabled, ActivClient will communicate with the smart card in GSC-IS mode. That mode is used to communicate with Department of Defense Common Access Cards (CAC). If this setting is disabled, ActivClient will communicate with the smart card in PIV mode. Smart card removal behavior policy setting in group policy 1. Navigate to <Name of Policy> Policy > Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies > Security Options. 2. Set the Interactive Logon: Smart card removal behavior policy to reflect the desired behavior in your organization. There are four options: No Action, Lock Workstation, Force Logoff, and Disconnect If a Remote Desktop Service Session. citrix.com 17

22 User Account Settings Map AD user account to the PIV authentication certificate Create alternate UPN 1. If it is not already running, start an instance of the Microsoft Management Console. Add the Active Directory domains and trusts snap-in. Right-click on Active Directory Domains and Trusts, click Properties. The Active Directory Domains and Trusts Properties dialog box is displayed. 2. In the Alternate UPN Suffixes textbox, enter upn.example.com, and click Add: 3. Click OK. citrix.com 18

23 upn.example.com is the suffix of the principal name in the Subject Alternate Name field of the PIV Authentication certificate on NIST PIV Test Card # 1: Create OU for PIV user accounts 1. If it is not already running, start an instance of the Microsoft Management Console. Add the Active Directory Users and Computers snap-in. 2. Right-click on the domain object, hover the cursor over New, and then select Organizational Unit. Name the new OU Smartcard Users. Click OK: citrix.com 19

24 Create user group 1. Right-click on the newly created Smartcard Users OU, hover the cursor over New, and click Group. Name the group G-Scope Smartcard Group. Note that the group scope is Global and the group type is Security: 2. Click OK. citrix.com 20

25 Create user account 1. Right-click on the Smartcard Users OU, hover the cursor over New, and click User. Fill out the New Object User dialog box as follows: Note that the user logon name matches principal name in the Subject Alternate Name field of the PIV Authentication Certificate on NIST PIV Test Card #1: citrix.com 21

26 2. Click Next. citrix.com 22

27 3. Provide a password, and click Next, and then click Finish. Add user to G-Scope Smartcard Group 1. Right-click on the NIST_PIV_01 PIV Authentication Cert user account, hover the cursor over All Tasks, and click Add to a group. Enter the following: 2. Click OK. Set smart card required for interactive logon 1. Right-click on the NIST_PIV_01 PIV Authentication Cert user account, and click Properties. Click on the Account tab. In the Account options section, deselect User must change password at next logon, and select Smart card is required for interactive logon: citrix.com 23

28 NOTE When you check the Smart card is required for interactive logon box, the operating system takes over user password management. It assigns a maximum-length password that is equivalent to 255 characters and ensures that it meets complexity requirements, effectively blocking the user from logging on to the network using a password. This can also be set via group policy. PKI certificate configuration Request KDC Certificate from your organization s issuing CA 1. Refer to steps 2 and 5 in Appendix D: Publishing Certificates in Active Directory for a graphical representation of the steps below. 2. Start an instance of the Microsoft Management Console (MMC). From the File menu, choose Add/Remove Snap In. From the Available snap-ins list, select Certificates, and click Add. The Certificates dialog box will appear. Select the local computer as the computer you want the snap-in to manage. Click Finish, and then click OK. 3. Navigate to Personal > Certificates. Right-click on Certificates, choose All Tasks, and click on Request New Certificate. The Certificate Enrollment wizard opens. Click Next. Select the appropriate Certificate Enrollment Policy. Click Next. citrix.com 24

29 4. Select Kerberos Authentication, and click Enroll. NOTE If Kerberos Authentication is not listed, you will need to adjust the enroll permissions in the Security tab of the Kerberos Authentication Certificate Template Properties using the Certificate Templates mmc snap-in on the issuing CA. The certificate is intended for the following purposes: citrix.com 25

30 Certificate file consolidation You should now have the following certificate files at hand: The NIST test PIV self-signed CA certificate: The NIST test PIV issuing CA certificates: NOTE Of the five NIST test PIV issuing certificates, the one that is relevant to the steps in the guide is RSA2048IssuingCACertificate.cer because it is in the PIV authentication certificate s trust chain. Your organization s exported RootCA certificate: Publish certificates to Active Directory certificate containers Using this method, the certificates are automatically propagated throughout. This way you do not have to manually install certificates in certificate stores on machines individually. 1. Refer to Appendix D: Publishing Certificates in Active Directory for a diagrammatic representation of the process that follows. NOTE You must run these commands using a user account with enterprise administrative privileges. Do not use an account that is a member of the domain admins group but not the enterprise admins group. citrix.com 26

31 2. Copy the certificate files to a directory. Run a command prompt. Change the prompt to that directory. Then run the following commands from the command prompt: Publish your organization s root CA certificate to Certification Authorities (RootCA) container (Refers to step 6 in Appendix D: Publishing Certificates in Active Directory) Syntax: certutil dspublish f <Your Organization s Root CA Certificate file>.cer Example: certutil dspublish f Root_CA_F2-DC-CA.cer Publish your organization s root CA certificate to NTAUTH certificates (NTAuth) container (Refers to step 7 in Appendix D: Publishing Certificates in Active Directory) Syntax: certutil dspublish f <Your Organization s Root CA Certificate file>.cer NTAuthCA Example: certutil dspublish f Root_CA_F2-DC-CA.cer NTAuthCA Publish the NIST test PIV root CA certificate to Certification Authorities (RootCA) container (Refers to step 8 in Appendix D: Publishing Certificates in Active Directory) Syntax: certutil dspublish f < NIST Test PIV Root CA Certificate file>.cer Example: certutil dspublish f Self-signedTrustAnchorCertificate.cer Publish the NIST test PIV issuing CA certificate to NTAUTH container (Refers to step 9 in Appendix D: Publishing Certificates in Active Directory) Syntax: certutil dspublish f < NIST Test PIV Issuing CA Certificate file>.cer NTAuthCA Example: certutil dspublish f RSA2048IssuingCACertificate.cer NTAuthCA Publish the NIST test PIV issuing CA certificate to AIA (SubCA) container (Refers to step 10 in Appendix D: Publishing Certificates in Active Directory) Syntax: certutil dspublish f < NIST Test PIV Issuing CA Certificate file>.cer subca Example: certutil dspublish f RSA2048IssuingCACertificate.cer subca citrix.com 27

32 Propagation does not occur until a group policy refresh. Manually force-refresh using the following command: Gpupdate /Force Enterprise PKI snap-in 1. To view the published certificates in the graphical user interface, you need the enterprise PKI snap-in. All of the relevant AD Containers can be viewed. However, it is not possible to add certificates to the AIA (subca) Container using the snap-in. NOTE If anything is showing as untrusted, refresh the group policy to ensure it propagates and is trusted. citrix.com 28

33 Virtual Delivery Agent (VDA) Test environment assumptions Operating system is 64 bit Windows 7 with Service Pack 1 Citrix Virtual Delivery Agent is The smart card middleware is 64-bit ActivClient Machine is domain-joined Prerequisites The VDA trusts your organization s root and intermediate certificate authorities. In other words, copies of the CA certificates for your organization s root and intermediate certificate authorities are located in the VDA s Local Computer Trusted Root Certification Authorities and Intermediate Certification Authorities stores, respectively. Configuration Steps Install middleware 1. Refer to Appendix E: Install ActivClient on Windows 7 x64 for detailed steps. NOTE Smart Card reader drivers are not required on the VDA. Install VDA for Windows Desktop OS 1. Perform the installation on the VDA machine console, not remotely via a remote desktop protocol such as RDP. 2. Insert the Citrix installation media, and run the AutoSelect.exe file: The XenApp and XenDesktop installer opens: citrix.com 29

34 3. Click Start for XenDesktop. Then click Virtual Delivery Agent for Windows Desktop OS: citrix.com 30

35 4. Select the Enable Remote PC Access option. citrix.com 31

36 NOTE For a production environment, you likely will want to use a master image. Refer to the Citrix Product Documentation site for more information about how to configure and use a master image: 5. For Core Components, install only the VDA. Do not install Citrix Receiver. citrix.com 32

37 NOTE Citrix Receiver is typically installed on the VDA in double-hop scenarios (when a user launches a XenApp session from within a XenDesktop session). If you intend to perform double-hop deployments with smart card Single Sign-on (Please note that double-hop deployments are outside the scope of the first edition of this guide): You must install Receiver on the VDA from the command line and add the /includesson command line switch or the Citrix Single Sign-on service component will not be installed when Receiver is installed. In addition, the build of Receiver that you want to use may not be the same Receiver build that ships with the VDA build (that is consumed by the VDA installation wizard). 6. Enter the FQDN of the Delivery Controller. For this example, it is a-ddc.f2.ctxs. NOTE There is no need to click Test connection if the Delivery Controller is not configured yet. (Which will be the case if you are following the steps in the guide sequentially.) Be absolutely sure the Controller address entered here is identical to the address you plan to use for the Delivery Controller later. 7. Click Next. citrix.com 33

38 8. Leave Features at default. citrix.com 34

39 9. Leave Firewall at default. citrix.com 35

40 A summary will be displayed: 10. Click Install. citrix.com 36

41 citrix.com 37

42 Delivery Controller Test environment assumptions Operating system is Windows Server 2012 R2. Citrix XenDesktop is version The Delivery Controller runs on a dedicated server (StoreFront is also installed on a separate dedicated server of its own.). No stand-alone database server is used. During Delivery Controller installation, SQL Server 2012 Express SP1 is automatically installed on and used by the Delivery Controller. Machine Management/Machine Creation Services (MCS) is not used. Microsoft Internet Information Services (IIS) is installed on the Delivery Controller, which possesses a server certificate with corresponding private key, and the server certificate is used to bind https to port 443 in IIS: Prerequisites Citrix License Server is up and running (configuring the License Server is outside the scope of this guide). The Delivery Controller trusts your organization s root and intermediate certificate authorities. In other words, copies of the CA certificates for your organization s root and issuing certificate authorities are located in the Delivery Controller s Local Computer Trusted Root Certification Authorities and Intermediate Certification Authorities stores, respectively. citrix.com 38