Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Configuring Kerberos auth when domain in FQDN does not match realm name (76954)

Last Updated: 1/5/2023Categories: InformationalTotal Views: 4488Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

This article provides information on how to configure Kerberos auth when domain in the FQDN does not match the realm name (Linux Connector).

For example, consider the case where the connector FQDN is "123.example.com" and the AD domain's realm name is "INTERNAL.AD".

To make Kerberos auth work properly in this case, a user within Active Directory must be configured with a service principal name (SPN) of https://123.example.com and then a keytab entry must be created within the /etc/krb5.keytab file on the connector using the password for that user.

Previously, this has been done by using the Windows ktpass command and then merging the keytab file produced by that command with the /etc/krb5.keytab file. However, that procedure does not work.

Solution

To resolve this issue:

On a Windows host within the domain:

Create a user to use for this purpose.

Run this command on the AD:

ktpass -princ HTTP/hostname-FQDN@REALM -mapuser user@REALM -crypto ALL -pass * -pType KRB5_NT_PRINCIPAL

For example, if the connector hostname-FQDN is conn.example.com, the realm is INTERNALAD and the user is someuser, then the command would be:

ktpass -princ HTTP/conn.example.com@INTERNALAD -mapuser someuser@INTERNALAD -crypto ALL -pass * -pType KRB5_NT_PRINCIPAL

Run this command to obtain the KVNO:

get-aduser -filter {name -like "username*"}  -prop Name,msDS-KeyVersionNumber

If /etc/krb5.keytab already exist, in the vIDM connector, backup the keytab file by running this command:

cp /etc/krb5.keytab /etc/krb5.keytab.backup

Run this command:

/opt/likewise/bin/ktutil

If /etc/krb5.keytab already exist, run this command:

read_kt /etc/krb5.keytab

Run this command:

addent -password -p HTTP/hostname-FQDN@REALM -k KVNO-from-step-3 -e RC4-HMAC

Note: This prompts for a password.

Run this command:

write_kt /etc/krb5.keytab

Run this command:

quit

Run this command:

chown horizon /etc/krb5.keytab

Run this command:

chmod 600 /etc/krb5.keytab

Run this command:

service horizon-workspace restart

Note: In step 7 above, if additional encryption types are desired, more addent commands can be run with other encryption types. Other valid encryption types include: AES256-CTS, AES128-CTS.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
Skyline Advisor 的访问要求 (82120)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Workspace ONE Access

VMware Identity Manager

Related Versions:

Take Our Survey

Support Assistant