1. Open firefox and enter: about:config in the address bar to enter the Settings page (not available in other browsers)
2. Search for “net.negotiate -auth. Trusted -uris” to change the value to your server host name. 3. Search for “net.auth.use-sspi” and double click to change the value to false.
4. Install KFW (no private kfw-4.1-amdc64.msi)
5. Copy the contents of a clustered /etc/krb5.conf file to C:\ProgramData\MIT\ os5\krb.ini and delete the path-related configuration.
[logging]
[libdefaults]
default_realm = HADOOP.COM
dns_lookup_realm = false
dns_lookup_kdc = false
ticket_lifetime = 24h
renew_lifetime = 7d
forwardable = true
udp_preference_limit = 1
[realms]
HADOOP.COM = {
kdc = plum01
admin_server = plum01
}
[domain_realm]
div>
Read More:
- CDH opens Kerberos and reports an error: ticket expired
- Authentication error occurred on remote connection, the required function is not supported
- Inexplicable exception 007: git error: authentication failed for
- Authentication failed under GitHub desktop
- Git authentication failed
- Cloning failed using an SSH key for authentication
- 【Linux】psql: FATAL: Ident authentication failed for user “username” Error and Solution
- Putty logs in and prompts no supported authentication methods available
- No supported authentication methods available
- psql: FATAL : password authentication failed for user “postgres”
- Mongodb connection authentication auth failed solution
- Git authentication failure solution, due to the problem of password modification
- Jedis exception resolution: noauth authentication required
- [Solved] MongoDB Insert Data Error: OperationFailure: Authentication failed…
- Passwd: authentication token manipulation error in Linux
- An authentication error occurred in the remote desktop connection
- Jedis operation redis report noauth authentication required
- Git push “fatal: Authentication failed ”
- Putty encountered an error when logging into alicloud CentOS: dis connected:No supported authentication methods available
- Solve the problem of keyboard interactive authentication with the SSH2 server failed