Set up iOS or iPadOS device with Company Portal and Entrust

 This article describes steps to configure Intune MDM with derived credentials (in this example the derived credentials are issued by Entrust). 

Set up iOS or iPadOS device with Company Portal and Entrust

  • Article

Enroll your device with the Intune Company Portal app to gain secure, mobile access to your organization's email, files, and apps. After your device is enrolled, it becomes managed. Your organization can assign policies and apps to the device through a mobile device management (MDM) provider, such as Intune.

During enrollment, you'll also install a derived credential on your device. Your organization might require you to use the derived credential as an authentication method when accessing resources, or for signing and encrypting emails.

You likely need to set up a derived credential if you use a smart card to:

  • Sign in to school or work apps, Wi-Fi, and virtual private networks (VPN)
  • Sign and encrypt school or work emails using S/MIME certificates

In this article, you will:

  • Enroll a mobile iOS or iPadOS device with Intune Company Portal.
  • Get a derived credential from your organization's derived credential provider, Entrust.

What are derived credentials?

A derived credential is a certificate that's derived from your smart card credentials and installed on your device. It grants you remote access to work resources, while preventing unauthorized users from accessing sensitive information.

Derived credentials are used to:

  • Authenticate students and employees who sign in to school or work apps, Wi-Fi, and VPN
  • Sign and encrypt school or work emails with S/MIME certificates

Derived credentials are an implementation of the National Institute of Standards and Technology (NIST) guidelines for Derived Personal Identity Verification (PIV) credentials as part of Special Publication (SP) 800-157.

Prerequisites

To complete enrollment, you must have:

  • Your school or work-provided smart card
  • Access to a computer or kiosk where you can sign in with your smart card
  • Your mobile device
  • The Intune Company Portal app for iOS and iPadOS installed on your device

Enroll device

  1. Open the Company Portal app for iOS/iPadOS on your mobile device and select the option to sign in from another device.

  2. Write down the onscreen code.

    Example image of Company Portal app with onscreen message and code.

  3. Switch to your smart card-enabled device and go to https://microsoft.com/devicelogin.

  4. Enter the code you previously wrote down.

    Example screenshot of the Company Portal website "Enter code" prompt.

  5. Insert your smart card to sign in.

  6. Return to the Company Portal app on your mobile device and follow the onscreen instructions to enroll your device.

  7. After enrollment is complete, Company Portal will notify you to set up your smart card. Tap the notification. If you don't get a notification, check your email.

    Example screenshot of the Company Portal push notification on device home screen.

  8. On the Setup mobile smart card access screen:
    a. Tap the link to your organization's setup instructions. If your organization doesn't provide additional instructions, you'll be sent to this article.
    b. Tap Begin.

    Example screenshot of the Company Portal Set up mobile smart card access screen.

  9. Switch to your smart card-enabled device and open IdentityGuard.

  10. Find the smart credential sign-in area and select the sign-in button.

  11. When you're prompted to select a certificate, pick your smart card credentials. Then select OK.

  12. Enter your smart card PIN.

  13. You'll be asked to choose from a list of actions. Select the one that lets you enroll for a derived mobile smart credential. The link or button might say I'd like to enroll for a derived mobile smart card credential.

  14. Select that you've successfully downloaded and installed the smart credential-enabled application. Then continue to the next screen.

  15. Enter information about your derived smart card credential.
    a. For the identity name, enter any name, such as Entrust Derived Cred.
    b. In the dropdown menu, select Entrust IdentityGudard Mobile Smart Credential.
    c. Continue to the next screen. You'll see a QR code with a numerical password under it.

  16. Return to your mobile device. On the Company Portal > Get QR code screen, tap Continue.

    Example screenshot of the Company Portal Get QR code screen.

  17. Tap Use Camera > OK.

    Example screenshot of a Company Portal prompt, asking permission to allow camera access.

  18. Scan the image of the QR code that's on your smart card-enabled device.

  19. Enter the numerical password that appears under the QR code.

    Example screenshot of the Company Portal Password Required screen, enter password field.

  20. Wait for Company Portal to finish setting up your device.

Next steps

After enrollment is complete, you'll have access to work resources, such as email, Wi-Fi, and any apps that your organization makes available. For more information about how to get, search for, install, and uninstall apps in the Company Portal see:

Comments

Post a Comment

Popular posts from this blog

VMware fix for Invalid manifest and ova file import failed errors

Image
Recently we got a OVA file for a virtual machine. The vendor instructions were to import the ova file in vmware Workstation, Player for Windows/Linux, Fusion for Mac, and VirtualBox as well.  The instructions were to take the available package and launch the VM with VMware workstation. The package contained  Module.mf, Module.ovf and Module-disk.vmdk and a Module.ova file. The .mf and .ovf file were 2 KB each whereas the vmdk was several gigs. The package also contained a Module.ova file which was several gigs as well. OVF           Open Virtualization Format MF             Manifest file VMDK       Virtual Machine Disk OVA           Open Virtualization Appliance The ovf file is a xml file that contains metadata for the ovf package The mf file contains the SHA1 hash codes of all files in the package The vmdk file is the disk image of the virtual machine,  VMware Workstation or VirtualBox. (vmdk format was originally developed by VMware and is an open format now). All of
Read more

SOAPUI - import certificate

Image
Note: SoapUI has two versions, one is open source and second Professional version. The open source can be download here . (confirmed link 12/19/2018). SSL Handshake issue:   There is an Issue in SoapUI version 5.3.0 (and 5.2.0 version) with SSL handshake error. It was resolved by updating below in vmoptions file ( refer here ). However, the error that shows up while trying to load wsdl is "Error loading WSDL" as below The fix is to Enable TLS 1.2 protocol for SOAP/REST calls in SoapUI, by ammending the vmoptions file to add the directive for TLS as (-Dsoapui.https.protocols=TLSv1.2). Refer here . Update: Version 5.5.0 does not have this issue. If you are on 5.3.0 better upgrade to 5.5.0 which is available now (Feb 2019). I had above issue as well as another issue reaching to https endpoint. Upgrade to 5.5.0 resolved issue. Select "Check for updates" under the Help menu and you will get option for upgrade. Select upgrade current version and accept all defaul
Read more

Session Timeout in Oracle Access Manager

Image
Session Timeout in Oracle Access Manager (OAM) The session lifetime and Idle timeout entries control how long a user's session is valid. In OAM, a user session is an object which represents an authenticated user. This object is stored in the server memory and if Database session persistence is enabled, this object is stored or available in the database. Each session is unique and is identified by both a userid and Session ID (session identifier), see screenshot below "OAM User Session Management".  A valid session means a user has been authenticated with OAM. A session can have following three states: 1) active 2) inactive 3) expired When a session is created it is in active state and is available as an object in the OAM. After a set time - idle timeout, the session moves or transitions to inactive state. And finally after the Session Lifetime time, the session is marked as expired. Expired sessions are removed from server memory. Read more about Session Lifetime
Read more