Product documentation
XenMobile Server
View PDF

Client certificate or certificate plus domain authentication

December 7, 2023
Contributed by: 
K C E

The default configuration for XenMobile is user name and password authentication. To add another layer of security for enrollment and access to the XenMobile environment, consider using certificate-based authentication. In the XenMobile environment, this configuration is the best combination of security and user experience. Certificate plus domain authentication has the best SSO possibilities coupled with the security provided by two-factor authentication at Citrix ADC.

For optimal usability, you can combine certificate plus domain authentication with Citrix PIN and Active Directory password caching. As a result, users don’t have to enter their LDAP user names and passwords repeatedly. Users enter user names and passwords for enrollment, password expiration, and account lockout.

Important:

XenMobile doesn’t support changing the authentication mode from domain authentication to some other authentication mode after users enroll devices in XenMobile.

If you don’t allow LDAP and use smart cards or similar methods, configuring certificates allows you to represent a smart card to XenMobile. Users then enroll using a unique PIN that XenMobile generates for them. After a user has access, XenMobile then creates and deploys the certificate used to authenticate to the XenMobile environment.

You can use the Citrix ADC for XenMobile wizard to perform the configuration required for XenMobile when using Citrix ADC certificate-only authentication or certificate plus domain authentication. You can run the Citrix ADC for XenMobile wizard one time only.

In highly secure environments, usage of LDAP credentials outside of an organization in public or insecure networks is considered a prime security threat for the organization. For highly secure environments, two-factor authentication that uses a client certificate and a security token is an option. For information, see Configuring XenMobile for Certificate and Security Token Authentication.

Client certificate authentication is available for XenMobile MAM mode (MAM-only) and ENT mode (when users enroll into MDM). Client certificate authentication isn’t available for XenMobile ENT mode when users enroll into legacy MAM mode. To use client certificate authentication for XenMobile ENT and MAM modes, you must configure the Microsoft server, the XenMobile Server, and then Citrix Gateway. Follow these general steps, as described in this article.

On the Microsoft server:

  1. Add a certificate snap-in to the Microsoft Management Console.
  2. Add the template to Certificate Authority (CA).
  3. Create a PFX certificate from the CA server.

On the XenMobile Server:

  1. Upload the certificate to XenMobile.
  2. Create the PKI entity for certificate-based authentication.
  3. Configure credentials providers.
  4. Configure Citrix Gateway to deliver a user certificate for authentication.

For information about Citrix Gateway configuration, see these articles in the Citrix ADC documentation:

Prerequisites

  • When you create a Microsoft Certificate Services Entity template, avoid possible authentication issues with enrolled devices by excluding special characters. For example, don’t use these characters in the template name: : ! $ () # % + * ~ ? | {} []

  • To configure Certificate-based Authentication for Exchange ActiveSync, see this Microsoft blog. Configure the certificate authority (CA) server site for Exchange ActiceSync to require client certificates.
  • If you use private server certificates to secure the ActiveSync traffic to the Exchange Server, ensure that the mobile devices have all necessary Root/Intermediate certificates. Otherwise, certificate-based authentication fails during the mailbox setup in Secure Mail. In the Exchange IIS Console, you must:
    • Add a website for XenMobile use with Exchange and bind the web server certificate.
    • Use port 9443.
    • For that website, you must add two applications, one for “Microsoft-Server-ActiveSync” and one for “EWS”. For both of those applications, under SSL Settings, select Require SSL.

Add a certificate snap-in to the Microsoft Management Console

  1. Open the console and then click Add/Remove Snap-ins.

  2. Add the following snap-ins:

    • Certificate Templates
    • Certificates (Local Computer)
    • Certificates - Current User
    • Certificate Authority (Local)

    Microsoft Management Console

  3. Expand Certificate Templates.

    Microsoft Management Console

  4. Select the User template and Duplicate Template.

    Microsoft Management Console

  5. Provide the Template display name.

    Important:

    Select the Publish certificate in Active Directory checkbox only if necessary. If this option is selected, all user client certificates are created in Active Directory, which might clutter your Active Directory database.

  6. Select Windows 2003 Server for the template type. In the Windows 2012 R2 server, under Compatibility, select Certificate authority and set the recipient as Windows 2003.

  7. Under Security, select the Enroll option in the Allow column for the specific users who are configured with PKI entity settings for XenMobile Server or the user groups that have the users configured with PKI entity settings.

    Microsoft Management Console

  8. Under Cryptography, ensure that you provide the key size. You later enter the key size when configuring XenMobile.

    Microsoft Management Console

  9. Under Subject Name, select Supply in the request. Apply the changes and then save.

    Microsoft Management Console

Adding the template to Certificate Authority

  1. Go to Certificate Authority and select Certificate Templates.

  2. Right-click in the right pane and then select New > Certificate Template to Issue.

    Microsoft Management Console

  3. Select the template that you created in the previous step and then click OK to add it into the Certificate Authority.

    Microsoft Management Console

Creating a PFX certificate from the CA server

  1. Create a user .pfx cert using the service account with which you logged in. The .pfx is uploaded to XenMobile, which then requests a user certificate on behalf of the users who enroll their devices.

  2. Under Current User, expand Certificates.

  3. Right-click in the right pane and then click Request New Certificate.

    Microsoft Management Console

  4. The Certificate Enrollment screen appears. Click Next.

    Microsoft Management Console

  5. Select Active Directory Enrollment Policy and then click Next.

    Microsoft Management Console

  6. Select the User template and then click Enroll.

    Microsoft Management Console

  7. Export the .pfx file that you created in the previous step.

    Microsoft Management Console

  8. Click Yes, export the private key.

    Microsoft Management Console

  9. Select Include all certificates in the certification path if possible and select the Export all extended properties checkbox.

    Microsoft Management Console

  10. Set a password to use when uploading this certificate into XenMobile.

    Microsoft Management Console

  11. Save the certificate onto your hard drive.

Uploading the certificate to XenMobile

  1. In the XenMobile console, click the gear icon in the upper-right corner. The Settings screen appears.

  2. Click Certificates and then click Import.

  3. Enter the following parameters:

    • Import: Keystore
    • Keystore type: PKCS #12
    • Use as: Server
    • Keystore file: Click Browse to select the .pfx certificate you created.
    • Password: Enter the password that you created for this certificate.

    Certificates configuration screen

  4. Click Import.

  5. Verify that the certificate installed correctly. A correctly installed certificate displays as a User certificate.

Creating the PKI entity for certificate-based authentication

  1. In Settings, go to More > Certificate Management > PKI Entities.

  2. Click Add and then click Microsoft Certificate Services Entity. The Microsoft Certificate Services Entity: General Information screen appears.

  3. Enter the following parameters:

    • Name: Type any name
    • Web enrollment service root URL: https://RootCA-URL/certsrv/ (Be sure to add the last slash, /, in the URL path.)
    • certnew.cer page name: certnew.cer (default value)
    • certfnsh.asp: certfnsh.asp (default value)
    • Authentication type: Client certificate
    • SSL client certificate: Select the User Certificate to be used to issue the XenMobile client certificate.

    Certificates configuration screen

  4. Under Templates, add the template that you created when configuring the Microsoft certificate. Don’t add spaces.

    Certificates configuration screen

  5. Skip HTTP Parameters and then click CA Certificates.

  6. Select the root CA name that corresponds to your environment. This root CA is part of the chain imported from the XenMobile client certificate.

    Certificates configuration screen

  7. Click Save.

Configuring credentials providers

  1. In Settings, go to More > Certificate Management > Credential Providers.

  2. Click Add.

  3. Under General, enter the following parameters:

    • Name: Type any name.
    • Description: Type any description.
    • Issuing entity: Select the PKI entity created earlier.
    • Issuing method: SIGN
    • Templates: Select the template added under the PKI entity.

    Credential Providers configuration screen

  4. Click Certificate Signing Request and then enter the following parameters:

    • Key algorithm: RSA
    • Key size: 2048
    • Signature algorithm: SHA256withRSA
    • Subject name: cn=$user.username

    For Subject Alternative Names, click Add and then enter the following parameters:

    • Type: User Principal name
    • Value: $user.userprincipalname

    Credential Providers configuration screen

  5. Click Distribution and enter the following parameters:

    • Issuing CA certificate: Select the Issuing CA that signed the XenMobile Client Certificate.
    • Select distribution mode: Select Prefer centralized: Server-side key generation.

    Credential Providers configuration screen

  6. For the next two sections, Revocation XenMobile and Revocation PKI, set the parameters as required. In this example, both options are skipped.

  7. Click Renewal.

  8. For Renew certificates when they expire, select ON.

  9. Leave all other settings as default or change them as required.

    Credential Providers configuration screen

  10. Click Save.

Configuring Secure Mail to use certificate-based authentication

When you add Secure Mail to XenMobile, be sure to configure the Exchange settings under App Settings.

Apps configuration screen

Configuring Citrix ADC certificate delivery in XenMobile

  1. Log on to the XenMobile console and click the gear icon in the upper-right corner. The Settings screen appears.

  2. Under Server, click Citrix Gateway.

  3. If Citrix Gateway isn’t already added, click Add and specify the settings:

    • External URL: https://YourCitrixGatewayURL
    • Logon Type: Certificate and domain
    • Password Required: OFF
    • Set as Default: ON

  4. For Deliver user certificate for authentication, select On.

    Citrix Gateway configuration screen

  5. For Credential Provider, select a provider and then click Save.

  6. To use the sAMAccount attributes in the user certificates as an alternative to User Principal Name (UPN), configure the LDAP connector in XenMobile as follows: Go to Settings > LDAP, select the directory and click Edit, and select sAMAccountName in User search by.

    LDAP configuration screen

Enable Citrix PIN and user password caching

To enable Citrix PIN and user password caching, go to Settings > Client Properties and select these checkboxes: Enable Citrix PIN Authentication and Enable User Password Caching. For more information, see Client properties.

Troubleshooting your client certificate configuration

After a successful configuration of the preceding configuration plus the Citrix Gateway configuration, the user workflow is as follows:

  1. Users enroll their mobile device.

  2. XenMobile prompts users to create a Citrix PIN.

  3. Users are then redirected to the XenMobile Store.

  4. When users start Secure Mail, XenMobile doesn’t prompt them for user credentials for mailbox configuration. Instead, Secure Mail requests the client certificate from Secure Hub and submits it to the Microsoft Exchange Server for authentication. If XenMobile prompts for credentials when users start Secure Mail, check your configuration.

If users can download and install Secure Mail, but during the mailbox configuration Secure Mail fails to finish the configuration:

  1. If Microsoft Exchange Server ActiveSync uses private SSL server certificates to secure the traffic, verify that the Root/Intermediate certificates installed on the mobile device.

  2. Verify that the authentication type selected for ActiveSync is Require client certificates.

    Microsoft ActiveSync properties screen

  3. On the Microsoft Exchange Server, check the Microsoft-Server-ActiveSync site to verify that client certificate mapping authentication is enabled. By default client certificate mapping authentication is disabled. The option is under Configuration Editor > Security > Authentication.

    Microsoft ActiveSync configuration screen

    After selecting True, be sure to click Apply for the changes take effect.

  4. Check the Citrix Gateway settings in the XenMobile console: Ensure that Deliver user certificate for authentication is ON and that Credential provider has the correct profile selected.

To determine if the client certificate was delivered to a mobile device

  1. In the XenMobile console, go to Manage > Devices and select the device.

  2. Click Edit or Show More.

  3. Go to the Delivery Groups section, and search for this entry:

    Citrix Gateway Credentials: Requested credential, CertId=

To validate whether client certificate negotiation is enabled

  1. Run this netsh command to show the SSL Certificate configuration that is bound on the IIS website:

    netsh http show sslcert

  2. If the value for Negotiate Client Certificate is Disabled, run the following command to enable it:

    netsh http delete sslcert ipport=0.0.0.0:443

    netsh http add sslcert ipport=0.0.0.0:443 certhash=cert_hash appid={app_id} certstorename=store_name verifyclientcertrevocation=Enable VerifyRevocationWithCachedClientCertOnly=Disable UsageCheck=Enable clientcertnegotiation=Enable

    For example:

    netsh http add sslcert ipport=0.0.0.0:443 certhash=609da5df280d1f54a7deb714fb2c5435c94e05da appid={4dc3e181-e14b-4a21-b022-59fc669b0914} certstorename=ExampleCertStoreName verifyclientcertrevocation=Enable VerifyRevocationWithCachedClientCertOnly=Disable UsageCheck=Enable clientcertnegotiation=Enable

Client certificate or certificate plus domain authentication
December 7, 2023
Contributed by: 
K C E
December 7, 2023
Contributed by: 
K C E

In this article

Site feedback | Your privacy choices footer linkYour Privacy Choices | Privacy and legal terms | Cookie preferences | Consent settings | docs.cloud.com
© 1999- Cloud Software Group, Inc. All rights reserved.