Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Informatica Data Quality 10.4.0
  • All Products

Table of Contents

Search

  1. Preface
  2. Command Line Programs and Utilities
  3. Installing and Configuring Command Line Utilities
  4. Using the Command Line Programs
  5. Environment Variables for Command Line Programs
  6. Using infacmd
  7. infacmd as Command Reference
  8. infacmd aud Command Reference
  9. infacmd autotune Command Reference
  10. Infacmd bg Command Reference
  11. infacmd ccps Command Reference
  12. infacmd cluster Command Reference
  13. infacmd cms Command Reference
  14. infacmd dis Command Reference
  15. infacmd dp Command Reference
  16. infacmd idp Command Reference
  17. infacmd edp Command Reference
  18. Infacmd es Command Reference
  19. infacmd ihs Command Reference
  20. infacmd ipc Command Reference
  21. infacmd isp Command Reference
  22. infacmd ldm Command Reference
  23. infacmd mas Command Reference
  24. infacmd mi Command Reference
  25. infacmd mrs Command Reference
  26. infacmd ms Command Reference
  27. infacmd oie Command Reference
  28. infacmd ps Command Reference
  29. infacmd pwx Command Reference
  30. infacmd roh Command Reference
  31. infacmd rms Command Reference
  32. infacmd rtm Command Reference
  33. infacmd sch Command Reference
  34. infacmd search Command Reference
  35. infacmd sql Command Reference
  36. infacmd tdm Command Reference
  37. infacmd tools Command Reference
  38. infacmd wfs Command Reference
  39. infacmd ws Command Reference
  40. infacmd xrf Command Reference
  41. infacmd Control Files
  42. infasetup Command Reference
  43. pmcmd Command Reference
  44. pmrep Command Reference
  45. Working with pmrep Files

Command Reference

Command Reference

Back Next

SwitchToKerberosMode

SwitchToKerberosMode

Configure the Informatica domain to use Kerberos authentication.
The SwitchToKerberosMode command uses the following syntax: 
SwitchToKerberosMode

<-administratorName|-ad> administrator_name
        
<-ServiceRealmName|-srn> realm_name_of_node_spn

<-UserRealmName|-urn> realm_name_of_user_spn

[<-SPNShareLevel|-spnSL> SPNShareLevel PROCESS|NODE]
The following table describes
infasetup
 SwitchToKerberosMode options and arguments:
Option
Argument
Description
-administratorName
-ad
administrator_name
Required. User name for the domain administrator account that is created when you configure Kerberos authentication. Specify the name of an account that exists in Active Directory.
After you configure Kerberos authentication, this user is included in the
_infaInternalNamespace
 security domain that the command creates.
If the domain uses a single Kerberos realm to authenticate users, specify the samAccount name.
If the domain uses Kerberos cross realm authentication, specify the fully qualified user principal name, including the realm name. For example:
sysadmin@COMPANY.COM
-ServiceRealmName
-srn
realm_name_of_node_spn
Required. Name of the Kerberos realm that the domain uses to authenticate users. The realm name must be in uppercase and is case-sensitive.
To configure Kerberos cross realm authentication, specify the name of each Kerberos realm that the domain uses to authenticate users, separated by a comma. For example:
COMPANY.COM,EAST.COMPANY.COM,WEST.COMPANY.COM
Use an asterisk as a wildcard character before a realm name to include all realms that include the name. For example, specify the following value to include all realms that include the EAST.COMPANY.COM name:
*EAST.COMPANY.COM
-UserRealmName
-urn
realm_name_of_user_spn
Required. Name of the Kerberos realm that the domain uses to authenticate users. The realm name must be in uppercase and is case-sensitive.
To configure Kerberos cross realm authentication, specify the name of each Kerberos realm that the domain uses to authenticate users, separated by a comma. For example:
COMPANY.COM,EAST.COMPANY.COM,WEST.COMPANY.COM
Use an asterisk as a wildcard character before a realm name to include all realms that include the name. For example, specify the following value to include all realms that include the EAST.COMPANY.COM name:
*EAST.COMPANY.COM
SPNShareLevel
-spnSL
SPNShareLevel
PROCESS|NODE]
Optional. Indicates the service principal level for the domain. Set the property to one of the following levels:
  • Process. The domain requires a unique service principal name (SPN) and keytab file for each node and each service on a node. The number of SPNs and keytab files required for each node depends on the number of service processes that run on the node. Recommended for production domains.
  • Node. The domain uses one SPN and keytab file for the node and all services that run on the node. It also requires a separate SPN and keytab file for all HTTP processes on the node. Recommended for test and development domains. Recommended for test and development domains.
Default is process.
0 COMMENTS
We’d like to hear from you!