Tag Archives: Workspace ONE Access

ADFS Integration with Omnissa Access (Mobile Only Traffic)

Important Terms used in this blog Web Theme Name: OMNISSAACCESS ADFS: Active Directory Federation Services Claims Provider: This is to add services as an Identity Provider in ADFS Relying Party Trust: This is to add services as Service Providers in ADFS Workingfoldername: Name of the folder you want to create 1. Introduction ADFS remains aContinue reading “ADFS Integration with Omnissa Access (Mobile Only Traffic)”

Omnissa Access DB Migration 

Introduction We’ve encountered numerous cases where customers have requested assistance with migrating both the UEM Database Server and Application Server, typically for two key reasons:  In addition to these, there are instances where customers also seek help migrating their Access Database. While these requests are not as frequent, they do occur. This brief blog willContinue reading “Omnissa Access DB Migration “

Guest Post – OKTA Identity Engine (FastPass) Device Trust

Pre-Requisites Procedure to configure Okta OIE Device Trust with Workspace ONE MDM. In Okta Admin Console, specify a mobile device platform (Workspace ONE UEM) and generate a secret key that you’ll enter in your Workspace ONE UEM “Okta Verify” managed app configuration. The key allows Okta to determine the management status of your targeted AndroidContinue reading “Guest Post – OKTA Identity Engine (FastPass) Device Trust”

Horizon Certificates to be used after legacy Connector migration from 19.03/19.03.0.1 to 22.09 (22.0x)

Introduction Migration of legacy connectors to 22.0x is a separate topic all together and if you’re interested in knowing more about it, kindly check the VMware Document here. This blog covers the use of Horizon Certificates post migration. If your use case has Horizon Virtual apps collection, make sure the connection servers or the HorizonContinue reading “Horizon Certificates to be used after legacy Connector migration from 19.03/19.03.0.1 to 22.09 (22.0x)”

Workspace ONE Access Integration with Ping – Logical Workflow

1. Introduction This blog talks about the logical workflow between Workspace ONE Access and Ping (or any Service Provider). You can follow the official VMware documentation that describes the actual Integration process. I’ve noticed that a lot of my customers don’t have a clear understanding on how the federation works. They basically end up loosingContinue reading “Workspace ONE Access Integration with Ping – Logical Workflow”

Resolving “There was a problem while getting the AirWatch opt-in status” error while doing an integration between Workspace ONE UEM and Access

1. Introduction Integrating Workspace ONE UEM and Access is the first step to achieving Single Sign On and Identity Management for the users. It gives the users a Unified catalog experience with both UEM and Access applications under one roof. In this blog I will not get into the details of the Integration but willContinue reading “Resolving “There was a problem while getting the AirWatch opt-in status” error while doing an integration between Workspace ONE UEM and Access”

Identifying the REALM for your On-Premise Workspace ONE Access Environment

1. Introduction Before we understand the concept of choosing the correct REALM for your environment, it is important to understand what it is and why do we need it? REALM (mentioned in upper case usually) is the domain over which the KDC (Key Distribution Center) has the ability or authority to authenticate the users.  ItContinue reading “Identifying the REALM for your On-Premise Workspace ONE Access Environment”