Handling an Authentication Failure

Updated on 2022-08-16 GMT+08:00

View PDF

Symptom

An authentication failure occurs during the commissioning and running of an example project.

Troubleshooting Process

There are many reasons that will cause an authentication failure. You are advised to perform the following steps for troubleshooting in different scenarios:

Check whether the network connection between the device where this application runs and the cluster is normal, and check whether the TCP and UDP ports required by Kerberos authentication can be accessed.
Check whether each configuration file is correctly read and stored in a correct directory.
Ensure that the username and keytab file are obtained according to the operation guide.
Check whether the configuration information is properly set before initiating an authentication.
Check whether multiple authentication requests are initiated in the same process. That is, check whether the login() method is called repeatedly.
If the problem persists, contact Huawei engineers for further analysis.

Authentication Failure Examples

"clock skew too great" is displayed during authentication.

Check the cluster time.
Check the time of the machine where the development environment is located. The difference between the machine time and the cluster time must be less than 5 minutes.

"(Receive time out) can not connect to kdc server" is displayed during authentication.

Check whether the content of the krb5.conf file is correct. That is, check whether the file content is the same as the service IP address configuration of KerberoServer in the cluster.
Check whether the Kerberos service is running properly.
Check whether the firewall is disabled.

An exception occurs when a client application submits a task to the Hadoop cluster, and the message "Failed to find any Kerberos tgt" or "No valid credentials provided" is displayed.

Check whether the kinit command is executed. If no, perform kinit authentication before submitting the task.

In the multi-thread scenario, when the process starts, call the loginfromkeytab function provided by Hadoop to log in to KDC to obtain TGT. Before submitting tasks, call the reloginFromKeytab function to update the TGT.

// After the first login succeeds, set user group information.
UserGroupInformation.loginUserFromKeytab(this.userPrincipal,this.keytabFile);
// Before the thread submits the task:
UserGroupInformation.getLoginUser().reloginFromKeytab();

If multiple scripts use the kinit command to authenticate the same user, run the export KRB5CCNAME=keytab_path command before running the kinit command in each script to ensure that the path specified by KRB5CCNAME in each script process is inconsistent.

Parent topic: Security Authentication

Previous topic: Preparing a Developer Account

Next topic: ClickHouse Development Guide (Security Mode)

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot