Not authorized Error on connection

vijaysy · November 30, 2021, 11:07am

Hi

We are using pay as you go for mqtt.
from today morning we started getting
org.eclipse.paho.mqttv5.common.MqttException: Not authorized
error on connection.

Credentials are same & correct from long time they are not updated.

Please help with this.

hivemq-support · November 30, 2021, 1:58pm

Hi @vijaysy,

Can you please share your cluster address as well as the clientID of the client that is getting the NOT_AUTHORIZED error?

Thank you,
Florian

vijaysy · December 1, 2021, 1:12am

Hi @hivemq-support

Address : 45a68d1525ab4fa7b8e21155cedf4e4d.s1.eu.hivemq.cloud

I don’t have client id since we generate it dynamically.

SShet · December 1, 2021, 8:53am

Hi @vijaysy

Thanks for sharing the cluster url.
Most likely when the password is incorrect then you will receive a “Not authorized” error on connection.

We are checking further, meantime can please try to change the password and do a quick test by using mqtt cli client as mentioned in the startup guide of MQTT CLI client. Please let us know if you still get the same error.

Kind regards,
Sheetal

vijaysy · December 10, 2021, 9:58am

Hi @SShet

It got fixed after created new user name and password.
also again we faced same issue on another cluster/broker.

Looks like it is recurring, can you pls look into it again

zingiber · December 10, 2021, 11:56am

@vijaysy, can you rule out copy/paste errors or typos in the password field?
So far all our tests have been successful.

vijaysy · December 18, 2021, 6:59am

Hi @zingiber

Yes, I double checked for errors and typos.

Can it be because of 2 or more clients getting connected with same client ID?
Since after restarting process I am not seeing this issue.

Also can we check broker side logs for URL?

zingiber · December 20, 2021, 8:19am

Hey vijaysy,

A second connection using the same clientId as that of a currently connected session will always lead to the broker closing the connection to the prior client. This mechanism is called client take-over and is mandated by the MQTT specification.

The “Not authorized” would make it seem like the new connection attempt was failing. Was this the case, or were already connected sessions losing their connections? Can you please share a clientId of affected clients?

Kind regards,
Finn

vijaysy · December 20, 2021, 4:18pm

Hi @zingiber

About Second connection explanation → I got it.

I am getting this exception from this line of client paho.mqtt.java/ClientState.java at 6f35dcb785597a6fd49091efe2dba47513939420 · eclipse/paho.mqtt.java · GitHub

I went through the client code.

We are getting this error message POST establishing the connection, while sending/pushing the message.

github.com

eclipse/paho.mqtt.java/blob/6f35dcb785597a6fd49091efe2dba47513939420/org.eclipse.paho.mqttv5.client/src/main/java/org/eclipse/paho/mqttv5/common/packet/MqttConnAck.java#L64

    
      
          
          
	private boolean sessionPresent;
          	private MqttProperties properties;
          
          
	public MqttConnAck(byte[] variableHeader) throws IOException, MqttException {
          		super(MqttWireMessage.MESSAGE_TYPE_CONNACK);
          		this.properties = new MqttProperties(validProperties);
          		ByteArrayInputStream bais = new ByteArrayInputStream(variableHeader);
          		DataInputStream dis = new DataInputStream(bais);
          		sessionPresent = (dis.readUnsignedByte() & 0x01) == 0x01;
          		reasonCode = dis.readUnsignedByte();
          		validateReturnCode(reasonCode, validReturnCodes);
          		this.properties.decodeProperties(dis);
          		dis.close();
          	}
          
          
	public MqttConnAck(boolean sessionPresent, int returnCode, MqttProperties properties) throws MqttException {
          		super(MqttWireMessage.MESSAGE_TYPE_CONNACK);
          		if (properties != null) {
          			this.properties = properties;
          		} else {

Unfortunately, I did not add logs for client ids. I don’t have em.

Is it possible to check broker logs, from broker URL details at your end?

vijaysy · December 20, 2021, 4:23pm

Strange part is, restart of the application is fixing this issue.

hivemq-support · December 21, 2021, 12:01am

Hi @vijaysy,

Have you tried running your code against a locally hosted HiveMQ broker?
From what you are describing my best guess would be that the client is not re-using the authentication credentials on automatic re-connect.
Could that be possible?

Regards,
Florian

vijaysy · December 21, 2021, 3:35pm

Hi @hivemq-support

Yes, that could be an issue.
I am deploying changes to capture clientId and user name & password
used while reconnecting.

Also will try to-reproduce with local broker.

vijaysy · January 11, 2022, 4:58pm

Hi All

There was a bug in code, in re-connect the password was not being set.
Thank you for the help & really sorry for inconvenience.

Thank you
Vijay

Topic		Replies	Views
CONNECT failed as CONNACK contained an Error Code: NOT_AUTHORIZED HiveMQ Commercial Offerings	1	3481	January 4, 2021
Connection not authorized from ioBroker MQTT Client HiveMQ Cloud	2	1297	January 7, 2022
Client is not authorized to connect HiveMQ Cloud	47	9860	June 30, 2023
Can no longer connect to broker HiveMQ Community Edition	3	131	August 2, 2024
How to diagnose "no authorization" error? HiveMQ Cloud	13	3023	February 7, 2022

Not authorized Error on connection

Related topics