Description of problem:
net ads should try to use the default krb5 credentials cache in case KRB5CCNAME is not defined. Lack of this is causing great confusion for users (especially since the error message can be a bit misleading).
# kinit admin
Password for admin@DOMAIN.EXAMPLE.COM:
# net ads join -k
Failed to join domain: failed to lookup DC info for domain 'DOMAIN.EXAMPLE.COM' over rpc: NT_STATUS_NO_SUCH_FILE
# KRB5CCNAME=/tmp/krb5cc_0 net ads join -k
Using short domain name -- DOMAIN
Joined 'SMBTEST1' to realm 'DOMAIN.EXAMPLE.COM
Version-Release number of selected component (if applicable):
See also https://bugzilla.redhat.com/show_bug.cgi?id=737810.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Cause: The net utility used for joining to Windows domains did not use the existing Kerberos credential cache.
Consequence: Users could not re-use their existing tickets to join Windows domains using Kerberos.
Fix: "net" has been fixed to use existing tickets from the default credential cache.
Result: Joining using "net -k" works with existing Kerberos tickets.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.