VMware Identity Manager 2.9.2

Last Modified: Sep 15, 2017 @ 2:09 pm

Navigation

💡 = Recently Updated

Planning

Identity Manager is a component of VMware Workspace ONE.

  • For Horizon, Identity Manager enables SAML authentication, web-based ThinApp, and integration of additional apps from Citrix and the web.
  • For full functionality, Identity Manager should be paired with AirWatch (not detailed in this post).

System and Network Configuration Requirements at VMware Pubs.

VMware Tech Paper VMware Identity Manager in a Multiple-Data-Center Configuration: active/standby in two datacenters, three nodes in each datacenter, SQL AlwaysOn Availability Group Listener.

VMware Blog Post What’s New in the VMware Workspace ONE App:

  • You can now reorder your bookmarked apps (browser only)
  • You can now search apps not just by name or category but also by app description.

Upgrade

Upgrading can be performed online, or offline. Both are performed from the command line. See Upgrading to VMware Identity Manager 2.9.1 at VMware Pubs for details. And see EUC CST Tech Notes – Upgrading VMware Identity Manager On-Premises Virtual Appliances – UPDATED! at VMware Communities.

Preparation

DNS Configuration

If you intend to build multiple appliances (3 or more) and load balance them, specify a unique DNS name for each appliance. The Load Balancing DNS name is different from the appliance DNS names. For example:

  • Appliance 1 = im01.corp.local
  • Appliance 2 = im02.corp.local
  • Appliance 3 = im03.corp.local
  • Load Balancing Name = identity.corp.com. This name is used both internally and externally.

You’ll need SSL certificates that match these names.

Each of these DNS names must have a corresponding reverse DNS pointer record.

  1. Create DNS records for the virtual appliances.
  2. Create reverse pointer records too. Reverse pointer records are required.

LDAP Accounts

  1. All accounts synced with Identity Manager must have First Name, Last Name, and E-mail Address configured. This includes the Bind account.
  2. Create a new Active Directory group for your Identity Manager users. The Domain Users group will not work.

SQL Database

If you want to build multiple Identity Manager appliances and load balance them, configure them with an external database (e.g. Microsoft SQL). Or you can follow Using embedded vPostgres in Production for VMware Workspace Portal VA 2.1 (2094258)

For a script that performs all required SQL configuration, see Configure a Microsoft SQL Database at VMware Pubs.

  1. The SQL Server requires SQL Server and Windows Authentication mode.
  2. In SQL Management Studio, create a New Query.
  3. Paste the SQL commands into the New Query window, and click Execute.

OVF Deployment

  1. In the vSphere Web Client, right-click a cluster, and click Deploy OVF Template.
  2. In the Select source page, browse to the identity-manager-2.9.2.0-….ova file, and click Next.

  3. In the Review details page, click Next.
  4. In the Accept License Agreements page, click Accept, and click Next.
  5. In the Select name and folder page, give it a name, select a folder, and click Next.
  6. In the Select storage page, select Thin Provision, select a datastore, and click Next.
  7. In the Setup networks page, select the network for the appliance. Click Next.
  8. In the Customize template page, select a time zone, and make a choice regarding Customer Experience Improvement Program.
  9. Expand Networking Properties.
  10. DNS and Gateway – In the Networking Properties section, enter the standard DNS and Gateway information.
  11. According to Install the VMware Identity Manager OVA File at VMware Pubs, the Domain Name and Domain Search Path fields are not used.
  12. Host Name – Enter a hostname for the first appliance. If you intend to build multiple appliances and load balance them, then each appliance needs a unique name that does not match the load balanced name. If you only want to build one appliance, then the appliance Host Name should match whatever users will use to access Identity Manager.
  13. IP Address – Enter the IP address that is configured in DNS for the host name. DNS reverse lookup for this IP address must resolve to the appliance Host Name. Click Next.
  14. In the Ready to complete page. Click Finish.

Setup Wizard

  1. Power on the appliance.
  2. Wait for the appliance to power on and fully boot.
  3. Go to https://im01.corp.local to access the Identity Manager Setup Wizard. Note: you must connect to the DNS name. Connecting to the IP address will cause problems during the database setup process.
  4. The browser might prevent you from connecting.
  5. To fix this, go to https://IPAddress/horizon_workspace_rootca.pem. You are only using the IP address temporarily.
  6. Copy the root certificate and save it to a file.

  7. Install the root certificate to the Trusted Root Certification Authorities store (either Current User or Local Computer will work).

  8. Close the browser and reopen it. Then connect the browser using the DNS name again. It should work without certificate errors this time.
  9. In the Get Started page, click Continue.
  10. In the Set Passwords page, enter passwords for the three accounts, and click Continue.

  11. In the Select Database page, change it to External Database. Note: this page will only function properly if your address bar has a DNS name instead of an IP address.
  12. Enter a JDBC URL similar to the following:
    jdbc:sqlserver://mysqlserver.corp.local;DatabaseName=saas
  13. Enter the credentials for the horizon SQL account and click Test Connection. Then click Continue.

  14. In the Setup Review page, click the link.

SSH – Enable Root Access

This is optional. Enabling root access lets you use WinSCP to connect to the appliance using root credentials. Instructions can be found at https://blogs.vmware.com/horizontech/2013/03/how-to-enable-ssh-in-horizon-workspace-virtual-appliances.html.

  1. Putty to the Identity Manager appliance.
  2. Login as sshuser.
  3. Run su and enter the root password.
  4. Run vi /etc/ssh/sshd_config.
  5. Scroll down to line 40 (PermitRootLogin).
  6. Press <i> on the keyboard to change to insert mode.
  7. Go to the end of the line and change no to yes.
  8. Press <ESC> to exit insert mode.
  9. Type :x to save the file and exit.
  10. Run /etc/rc.d/sshd restart.

Configuration

  1. Login to the webpage as the admin user.
  2. You should be on the Identity & Access Management tab.
  3. On the top right, switch to the Setup view.
  4. On the left, switch to the User Attributes sub-tab.
  5. Scroll down. Check the boxes next to distinguishedName and userPrincipalName. Click Save.
  6. On the top right, switch to the Manage view.
  7. Click Add DirectoryAdd Active Directory over LDAP/IWA.
  8. Change it to Active Directory (integrated Windows Authentication). Note: Domain Controllers are selected at random. You can override this by creating the file domain_krb.properties on the appliance. See About Domain Controller Selection (domain_krb.properties file) at VMware Pubs.
  9. Enter the Active Directory domain DNS name. Scroll down.
  10. Enter credentials that can join the appliance to the domain.
  11. Enter the LDAP Bind credentials. Click Save & Next.
  12. Select the domains you want to sync, and click Next.
  13. In the Map User Attributes page, click Next.
  14. In the Select the Groups page, click the plus icon to add a DN.
  15. Enter a Base DN in LDAP format, and click Find Groups.
  16. Click Select.
  17. Search for your Identity Users group and select it. Don’t select Domain Users. It won’t work.
  18. Click Next.
  19. In the Select the Users page, click Next.
  20. In the Review page, click Edit.
  21. Select a more frequent sync schedule, and click Save.
  22. Click Sync Directory.

  23. You can click the link to view the Sync log.
  24. You can also click the directory name, and then click Sync log to view the log.

  25. Sync Settings can be changed by clicking the button on the right.

Logon Experience

  1. Go to Identity & Access Management > Setup > Preferences.
  2. On the bottom, Identity Manager 2.9.1 lets you optionally hide the Domain Drop-Down menu. Then select the unique identifier that Identity Manager will use to find the user’s domain (typically UPN).
  3. The user will be prompted to enter the unique identifier.

Administrators

  1. You can promote individual users (but not groups) to administrators. In the Admin console, on the top left, click the Users & Groups tab.
  2. Switch to the Users sub-tab.
  3. Click a username.
  4. Scroll down. Change the Role drop-down to Administrator. Click Save.

License

  1. On the Appliance Settings tab, on the left, click License.
  2. On the right, enter the license key, and click Save. A Horizon Advanced or Horizon Enterprise license key will work.

Certificate

  1. Use OpenSSL or similar to create the certificate in PEM format. If you have a .pfx, you can use OpenSSL to convert from pkcs12 to PEM. Also use OpenSSL to convert the private key to RSA format.
  2. On the top, click the Appliance Settings tab,
  3. On the left, click the VA Configuration node.
  4. On the right, click Manage Configuration.
  5. Login as your admin account.
  6. On the left, click Install Certificate.
  7. On the right, delete the certificate and key that are currently displayed.
  8. Paste in the new PEM certificate and RSA private key. Paste every certificate in the chain: server + intermediate + root. Click Save.
  9. Click OK to restart the appliance.
  10. After rebooting, if you close the browser and reopen it, the certificate should be valid and trusted.

SMTP

  1. On the top, click the Appliance Settings tab
  2. On the left, click the SMTP node.
  3. On the right, enter your mail server information, and click Save.

Kerberos Authentication

  1. On the top, go to the Identity & Access Management tab.
  2. On the right, change to the Setup view.
  3. On the left, click the Connectors sub-tab.
  4. Click the blue hostname link for the Connector.
  5. Switch to the Auth Adapters tab. You may enable Kerberos or other authentication adapters from this page by clicking the Adapter Name.
  6. Kerberos lets users Single Sign-on to the Identity Manager web page. It only works for Windows clients. And the Identity Manager FQDN must be in Internet Explorer’s Local Intranet zone.
  7. Enter sAMAccountName as the Directory UID Attribute.
  8. Check the box next to Enable Windows Authentication and click Save.
  9. After enabling the adapter, go to Identity & Access Management > Setup > Network Ranges.
  10. Click Add Network Range.
  11. Give the Network Range a name.
  12. Enter an internal IP Range, and click Save.
  13. Go to Identity & Access Management > Manage > Policies.
  14. Click the default Policy (default_access_policy_set).
  15. Click the plus icon to add a Policy Rule.
  16. Select the Network Range you just created.
  17. For user is trying to access content from, set it to Web Browser.
  18. Identity Manager 2.9.1 adds a Edit Groups button to policy rules. This allows different authentication methods for different groups. When enabled, Identity Manager asks the user for username only, and then looks up group membership to determine which authentication methods should be used. See Configuring Access Policy Settings at VMware Pubs.
  19. Select Kerberos as the first authentication method.
  20. Select Password as the second authentication method. Click OK.
  21. Drag the new Policy Rule to move it to the top. Then click Save.

Customize Appearance

  1. If you go to Identity & Access Management > Setup > Custom Branding, on the Names & Logos tab you can change the browser’s title and favicon.
  2. If you then switch to the Sign-In Screen page, you can upload a logo, upload an image, and change colors.
  3. If you go to Identity & Access Management > Manage > Password Recovery Assistant, you can configure a link to a password recovery tool or change the Forgot password message.
  4. If you scroll down you can optionally Show detailed message to End User when authentication fails.
  5. Click Catalog, and then click Settings.
  6. On the left, click User Portal Branding.
  7. Make changes to Logos, colors, etc.

Load Balancing

TLS 1.0 is disabled in Identity Manager 2.6 and newer. If your load balancer does not support TLS 1.2, then see 2144805 Enabling TLS 1.0 protocol in VMware Identity Manager 2.6. NetScaler MPX/SDX added TLS 1.2 on the back end in 10.5 build 58. NetScaler VPX added TLS 1.2 on the back end in 11.0 build 65.

If you want to build multiple Identity Manager appliances and load balance them using NetScaler, then see http://www.carlstalhood.com/VMware-Identity-Manager-Load-Balancing

For F5 load balancing, see EUC CST Tech Notes – IDM Steps by steps 3 node cluster – v4.pdf at VMware Communities

Resources

View Administrator – Enable SAML Authentication

  1. Login to View Administrator.
  2. On the left, under View Configuration, click Servers.
  3. On the right, switch to the Connection Servers tab.
  4. Select a Connection Server, and click Edit.
  5. On the Authentication tab, change Delegation of authentication to VMware Horizon to Allowed.
  6. Click Manage SAML Authenticators.
  7. Click Add.
  8. In the Label field, enter a descriptive label.
  9. In the Metadata URL field, enter the Identity Manager FQDN.
  10. In the Administration URL field, enter the Identity Manager FQDN, and click OK.
  11. If you see a certificate error, click View Certificate, and then click Accept.
  12. Or click OK if server’s identity was verified.
  13. Click OK to close the Manage SAML Authenticators window.
  14. Horizon 7.2 adds a Workspace ONE mode, which forces all Horizon Clients to connect through Identity Manager instead of directly to the Connection Servers. Delegation must be set to Required before Workspace ONE mode can be enabled.
  15. The Horizon Administrator dashboard shows you the status of the SAML Authenticator.

Identity Manager – Enable View Pools

Separate Horizon View Connection Server groups (e.g. multi-datacenter) can be configured in failover order. See Configure Failover Order of Horizon View and Citrix-based Resources at VMware Pubs.

  1. Back in the Identity Manager Admin Portal, go to Catalog > Application Catalog.
  2. Click Manage Desktop Applications, and click Horizon View On-Premises.
  3. Click one of the connectors.
  4. Check the box next to Enable Horizon View Applications and Desktops.
  5. Enter the address of a Horizon Connection Server (or load balanced FQDN). Note: reverse IP lookup must be functional for this DNS name.
  6. Enter View Administrator credentials in userPrincipalName format. The account needs at least Read Only Administrator access to Horizon.
  7. Notice the link to Add Horizon Pod. This is for Could Pod Architecture.
  8. Deployment Type can be Automatic or User-Activated. User-Activated means users have to go to the App Center to add the icons to the My Apps portal.
  9. Specify the Viewpool sync frequency, and click Save. New pools created in Horizon Administrator don’t show up in Identity Manager until a sync is performed.
  10. Near the top of the screen you might see red text. Click Invalid SSL Cert.
  11. In the Certificate Information page, click Accept.
  12. Near the bottom of the page click Sync Now. Note: whenever you make a change to the pools in View Administrator, you must either wait for the next automatic Sync time, or you can return to this screen and click Sync Now.
  13. If sync fails, see VMware 2091744 Synchronizing VMware Horizon View Pool in Workspace Portal fails with the error: Failed to complete View sync due to a problem with the View Connection Server.
  14. Then click Save and Continue. Note: whatever groups are entitled to Horizon Pools and Applications must also be synced (Active Directory) with Identity Manager.
  15. In the Identity Manager Admin console, on the Catalog tab, you can see the View icons. Only the pools in the root Access Group are synced.
  16. Click an icon and make sure entitlements are listed. Only AD groups synced to Identity Manager will be displayed. Domain Users won’t sync to Identity Manager, so entitle the pools to some other AD group. If you make changes in Horizon Administrator, then manually resync the connector.
  17. If you check the box next to one of the icons, you can place the icon in a Category by clicking the Categories button near the top right and entering a category name.
  18. If an existing category doesn’t match your needs, enter a new category name and click Add.
  19. Then check the box next to the new category.
  20. The category is then displayed next to the catalog item.

Identity Manager – Horizon URLs

  1. In the Identity Manager administrator interface, go to Identity & Access Management > Setup > Network Ranges.
  2. You can edit the default range or add a new range.
  3. Specify the Horizon URL for the IP range. You can have different Horizon Client Access URLs for different IP ranges (e.g. internal vs external). For external users, the URL points to Access Points or Horizon Security Servers.

Identity Manager User Portal

  1. When a user logs in to the Identity Manager web page the pool icons will be displayed.
  2. You can use either Horizon client or Browser for opening a pool. On the top right, click your name, and click Settings.
  3. On the left, click Preferences.
  4. Make your choice and click Save.
  5. To mark an icon as a Bookmark, click the bookmark icon next to each app.
  6. Or click an app icon to open the app’s Description page, and then click Bookmark.
  7. Then you can click Bookmarks tab to display only icons that are marked as Bookmarks.
  8. If you enabled categories, they are listed in the left side of the page. Only the icons in that category are displayed.

53 thoughts on “VMware Identity Manager 2.9.2”

  1. Figured I’d give this a shot before opening a case. In the process of standing up an On-Prem AirWatch 9.1.3, IdM 2.9.1 environment. So far got everything deployed and got the integration between IdM and View (7.0.3 I believe). It appears most of my entitlements synced up, however I’m seeing something weird. Hopefully, you (or someone) has seen it and can save me the headache of support…

    All the pools sync, there is one particular pool (possibly more, but this one affects me so I noticed it), that in the View Admin console has 8 users entitled to it. When it syncs with IdM, it now has 5 users entitled to it. in the IdM Catalog One of the users is a generic user and is missing a required attribute, and they won’t be accessing IdM anyway, so that one I don’t care about. However the other two missing users are my domain account and my co-worker’s domain account. These are just typical domain accounts, that have been successfully synced to the IdM user directory (via AirWatch). The one thing that I notice is that the two of us have accounts in our parent domain (also synced, the user accounts appear in IdM with their respecive domain attribute) with the same “username”.

    So for example, I’ve got domainA\userY and domainB\userY

    My View pool has domainB\userY entitled to it. IdM contains users for userY in domainA_FQDN and domainB_FQDN.in it’s User repository. Am I missing something to “help” IdM associate the correct “userY” with my View Pool?

    Be happy to explain more if needed. I’m stumped.

    Thanks for any help you, or anyone else, can provide.

    Rusty

  2. Hi Carl,

    Maybe you or some other reader also encountered the following;

    We have a case in which have a new separated Horizon Pod for Win10, and an ‘old’ pod for Win7.

    The pod for Win10 is just upgraded to 7.2, and this pod works as expected, desktops are running through client and browser (blast). but when using this desktops through Identity Manager (2.9.2) the desktop is only to be opened through the client, when opening it from IM in the browser it shows a ‘page can’t be found.

    the pod for win7 with horizon 6.2 though is able to be used from the connection servers, client and browser and through the same identity manager without a problem.

    might there be an issue with IDM2.9.2 Horizon7.2? Or is there a setting i missed?
    we had a working situation with IDM 2.9.1 Horizon 7.1.

    SAML authentication is set to allowed and is enabled.

    Thanks in advance for thinking with me, regards

      1. yes, also the horizon7.2 pod is using UAG(2.9.0). with the external url to this gateway, using without IM it is working perfectly, with client and through browser.

        the IM is not connected through UAG, but don’t expect this should give issues like this?

  3. Hi Carl,
    Could you help me with configuration vIDM?
    I try to configure SSO for Mobile Devices and Laptops and integrate this with AirWatch.
    Main idea it’s Kerberos authentification through Workspace Portal on laptops when it in intranet also through managed Workspace ONE app with AirWatch Profile at other Native and Web apps on iOS, Android and Windows Phone platforms from Internet.
    I done step-by-step yours instalation guide, thank you for your great job, but I have some problem. When I change Identity manager FQDN to load-balancer name Kerberos stopted worked, but I can authentificate with my domain credential trougth login form. If I change IdP Hostname in Identity and Access Managment -> Identity Providers -> WorkspaceIDP_​_​1 from public (load-balanced) name to local domain name, Kerberos start working again but I can’t authentithicate from internet.

  4. hi carl,
    i want to download vmware identity manager 2.4.1 . pls help me..i could not download from vmware. and i dont find any other download link from any resource.

  5. Hi Carl, great article. to start with. I am trying vidm in lab followed this doc.
    connection server url – https://consrv-01.domain.local, vidm fqdn – https://sso.domain.local

    what i am seeing is user acess https://sso.domain.local and login. When try to launch any view application (html access) it redirects me to connection server url to launch the application.

    Is this the way its supposed to work or i am missing something. if user connects from internet how should the connection server be exposed in internet.

    1. Identity Manager is nothing more than a portal that authenticates users and displays your icons.

      When connecting remotely, the PCoIP or Blast connection needs to be proxied through another machine. Identity Manager does not perform this proxy function. Instead, you need Security Server or Access Point to handle those connections.

      1. Hi carl,
        Thanks for the replay, Say I have a access point configured for my connection server at url access.domain.local.
        while configuring VIDM where should I mention the accesspoint URL so that applications are launched through access point URL instead of connection server.

        1. Network Range. After you integrate View with Identity Manager, go to Identity & Access Management > Setup > Network Ranges, add/edit, and there’s a Client Access URL Host.

  6. Hi Carl,
    Excellent article. vIDM 2.8 in my installation is not stable – CPU spikes up to 100% and crashes after few minutes. Have you seen CPU spiking issue in your installation? Any idea how to fix it

    1. Everyone experiencing this issue using SQL? I’m still utilizing the internal Postgres DB replicated across 3 nodes and haven’t seen this issue.

      1. Chad, using the internal Postgres DB here and having the issue. It seems to not occur until after setting the load balancer FQDN, but that’s pure speculation.

  7. Hi Carl,
    to install the second vIDM node, did you just clone the first one ? Is there anything else needed from SQL side, or the second vIDM appliance will point to the same SQL database and get same configuration ?

    I´m planning to install a couple of vIDM appliances and I have that doubt, if just a simple external SQL database is enough or has to be Always on technology or something like that.

    Thank you.

    1. You generally want HA for SQL too. But yes, simply clone and it connects to same SQL. Note, VMware wants you to have three appliances for HA. And IDM 2.8 is available now.

  8. Hi Carl,

    I have an issue with the Authentication with vIDM and Kerberos, I have RDSH App and i tried to connect from the vIDM but the SSO not worked , it is only worked from the user machine till the vIDM but when i try to access the RDSH App it is asking for authentication:

    My environment is:

    2 vIDM (HA)
    2 Access Point (HA)
    2 Connection Server (HA)
    2 RDS Servers
    load balance for Access Point

        1. Kerberos uses tickets for authentication, not passwords. When vIDM talks to Horizon, it needs to send the user’s password to Connection Server so Connection Server can do SSON to the Horizon Agent. Since there’s no password, it’s not possible to do SSON.

          Alternatively, if there’s no password, Connection Server can create a user certificate (TrueSSO), and use that for authentication to the Horizon Agent. TrueSSO is another server.

      1. Hi Carl, could you please how can i use CS LB in the vIDM and how can the user not distributive when one of the CS go down.

  9. Love your blog, it has proved a most helpful tool, hoping you might be able to help with an issue:-) I’m using vIDM 2.7.1 and Access Point 2.7.2 as a reverse proxy for vIDM. When I try and access the URL from the outside and login I get a spinning circle and if you hit refresh it logs in but is pretty much unusable. It seems like the documented proxypatterns and unsecuredpatterns are missing needed information or are missing needed data. Have you come across this issue? Thanks

  10. Great Article!

    With the Access Point, is there anything special needed to get it to work correctly? I deployed it and can get to the login page but then it redirects me back to the internal name of my Identity Manager. I’m guessing it’s because the FQDN isn’t correct but when i try to change it, I get an error that it won’t change it on the manager and idp. Thoughts?

    1. Are you using the special 2.6 version that doesn’t work with Horizon? There are separate instructions for Identity Manager on Access Point.

      1. Hi Carl, I´m using 2.6 version on-premise with Horizon 7 (connection server + Access Point) + AppVolumes 2.9. On View all works fine but with IDM user domain login not is possible.

        Thank you.

  11. Carl Please note that we should not pre-popluate the data base information. We also should not have to give the appliance DB_OWNER role as this has caused issue as well on the database side with the appliance. We should always use the provided script as it builds everything required out the gate and sets the correct permissions. (very common issue is not using this and or wanting to change the database name and or user)

    We do know of the using as you note of the IP address will not allow the configuration to proceed

    Unable to complete the configuration of VMware Identity Manager appliance
    Configuration of Identity Manager fails with error:
    Invalid organization name. Chosen name (null) includes invalid characters.
    Cause
    This issue occurs when the appliance is accessed with an IP address in the URL instead of FQDN

    We also note that any change to the Certificate and or FQDN will require a re-enable of the WORKSPACE ONE interface. Otherwise we will not be able to login.

    After enabling the Workspace ONE GUI interface, and then changing the FQDN and or Certificate of the appliance, and then attempting to log back in to VMware Identity Manager error message “Request Failed” “Please Contact your IT Administrator” message
    Resolution
    Log into the VMware Identity Manager htps://FQDN , choose the local users option and login as the “admin” account and password. Once logged in then navigate to the Catalog, Settings, New End User Portal UI tab.
    Select the “Enable New Portal UI” option

    Please also note that if you already have a Load balancer and or reverse proxy in place you do not gain anything by using them with your load balancer other than pain suffering and nightmares. With the load balancer already doing SSL termination already there is not direct access back to vIDM. Access Point was thought of for vIDM as an alternative if you did not have a LB or Reverse proxy already in place.

    1. Hi Robert,

      Thanks for your observations. I made some changes to the SQL and Load Balancing FQDN sections. Let me know if you notice anything else that needs to be corrected.

  12. Hi Carl, great writeup, i’m hitting problems with FQDN and a local domain name of.local. We have a wildcard for our external services say example.com and an internal name of example.local. if I deploy the appliance with FQDN of .workspace.example.co.uk I can then assign the wildcard cert but cannot get Kerberos to work even with SPNs added. If I deploy it with workspace.example.com and put an internal CA cert on it then Kerberos works fine but workspace.example.co.uk does not work as it redirects the url back to workspace.example.local which obviously cant be reached externally. we are not using any load balancers just a single appliance.

  13. Hi Carl,May I ask you a question?
    I run into trouble about reuse same FQDN to re-deploy vIDM after replace it self-sign certificate, I got the error about the certificate as below:

    com.vmware.horizon.svadmin.exception.AdminPortalException: org.springframework.web.client.ResourceAccessException: I/O error on GET request for “https://HZ-IDMV-02.CLOUD.CCDE.CNPC/SAAS/API/1.0/REST/system/bootstrap/initialize”:Host name ‘HZ-IDMV-02.CLOUD.CCDE.CNPC’ does not match the certificate subject provided by the peer (EMAILADDRESS=unknown@vmware.com, CN=HZ-IDMV-02.CLOUD.CCDE.CNPC, OU=Horizon-Workspace, O=VMware, L=Palo Alto, ST=california, C=US); nested exception is javax.net.ssl.SSLPeerUnverifiedException: Host name ‘HZ-IDMV-02.CLOUD.CCDE.CNPC’ does not match the certificate subject provided by the peer (EMAILADDRESS=unknown@vmware.com, CN=HZ-IDMV-02.CLOUD.CCDE.CNPC, OU=Horizon-Workspace, O=VMware, L=Palo Alto, ST=california, C=US) at com.vmware.horizon.svadmin.service.ApplicationSetupService.isFirstOrgAndAdminUserSetup(ApplicationSetupService.java:196) at com.vmware.horizon.svadmin.controller.AdminPortalShortcutsController.doGet(AdminPortalShortcutsController.java:44) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497)

    Could you help me fix the problem?

  14. Hi Carl.. an awesome article.. its my first time exploring vIDM, can you help me the steps on cert PEM creation …
    “1.Use OpenSSL or similar to create the certificate in PEM format. If you have a .pfx, you can use OpenSSL to convert from pkcs12 to PEM. Also use OpenSSL to convert the private key to RSA format.”

  15. Carl

    Thanks for the article, I would like to know your feedback on the product and how it compares to industry leading IDaaS products such as OKTA?

    Thanks

    Stu

    1. I’m more interested in the Horizon View integration. And AirWatch. For web-app SSON, there are many products that can do that. It’s not my expertise so I can’t say if one is better than another.

  16. So when i’m deploying the OVA file for the first Identity Manager appliance (I will load balance behind a pair of nertscalers) I should make the appliance hostanme FQDN “IM01.domain.local” on the OVA setup, not “identity.corp.com” in the setup?
    (you show “identity.corp.com” not “im01.corp.local” in your screenshot above with the OVA setup)

    – the connector on my im01 (I used identity.domain.com in the ova setup) shows “identity.domain.com” not im01.domain.local)

    – In the netscaler LB write up, you show naming the cloned appliance im02.corp.local

    I guess i’d like to know what is different about setting up the first IM appliance when you will be load balancing, should the fqdn in the first ova setup be an individual name or “identity”?

    1. If you’re not load balancing then the single appliance should be named the same as what users will use to access it. If load balancing then each appliance needs a unique name. I should probably clarify that and update the screenshots accordingly.

    2. Aaron, I updated the screenshots to reflect the load balancing scenario. I also figured out a database issue I was having and updated the instructions accordingly. This also fixed some cloning issues. Let me know if you notice anything else that needs to be fixed. Thanks.

        1. Configuration does not work properly unless you are connected to the appliance using an FQDN instead of IP. However, most browsers won’t allow the connection because of the untrusted cert. It would have been easier if VMware included a self-signed cert instead of a CA-signed cert.

  17. Great article, thank you very much! This was a HUGE help, especially with the netscaler article to go with it!
    One question on the SSL certs, each appliance (IM01.corp.pri and IM02.corp.pri) will have a cert for the “corp.pri” [corp.pri being a msft enterprise ca cert) AND a cert for identity.corp.COM [COM being a public cert]?
    Can i just use a public wild card for the IM01/IM02 and Identity, making them all .com (My internal domain is .pri), so it’s one cert (Not a SAN cert)? – name the fqdn’s “IM01.corp.com” and “IM02.corp.com” and “Identity.corp.com” using the same wildcard cert? (With DNS entries to match)

    How does the Identity manager play with the new Access Point for Horizon?

    1. I think public certs on each appliance should be fine. Each appliance needs a unique hostname so it can join the domain correctly.

      I believe a future release of Access Point will provide remote connectivity to Identity Manager. VMware mentioned they borrowed the auth components from Identity Manager to place on Access Point. Smart Card is a good example of this.

Leave a Reply