[Request] Longer MQTT-Username

[Sinned42]

Is your feature request related to a problem? Please describe.

I am using flespi.io as a broker for my MQTT.
Flespi.io uses tokens instead of Username and Password - unluckyly 64 characters, but only 32 characters are accepted.

Describe the solution you'd like

I suggest doing some changes in code:

configuration.h line 20
#define MQTT_MAX_USERNAME_STRLEN 64

MqqtAdminView.vue line 58
<input type="text" class="form-control" id="inputUsername" maxlength="64"

Best regards,
Sinned42

Describe alternatives you've considered

No response

Additional context

No response

[tbnobody]

This is something what I can implement after 15. Nov.
Please see #285
Currently this type is used to parse the binary blob for older devices. If I change this now it's no more possible for them to upgrade to the new config format.

[Sinned42]

Perfect, thank you. Time doesn't matter, I put my username direct in MqttSettings.cpp and it worked so far for me.

[m0tschi]

I appreciate it a lot, may you can do the same for the passwords? :)
thank you for all the improvements!

[OgerTours]

I check it with ee5b5b1 build and unfortunatly it's still not allowing to put more than 32 chars into username field.

Can some please check and/or confirm?

[tbnobody]

What error message are you getting?

The UI itself allows a lot of characters...

PS: Did you refresh the web UI? (e.g. F5 or CTRL+F5)

[OgerTours]

Sorry, my stupid fault, I fully need to refresh the browser page, seems that browser was caching the page contnet and doesn't allow it to put more than 32 chars. Now it's working. Sorry for confusion.

[tbnobody]

May I ask which browser you are using? (With my Vivaldi which uses the chromium engine the ETAG headers are working pretty well and I just have to reload (just F5) the page to get the new changed content)

[OgerTours]

I use the Firefox Browser. You can perform a page reload with STRG+R or Shift+Click on the reload symbole.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns.