[Bug]: admin key not being set, generate button makes no sense

[pleasantone]

Before submitting

• I have searched existing issues to make sure this bug hasn't already been reported
• I have updated to the latest version of the software to verify the issue still exists
• I have cleared cache/cookies/storage or tried in a private/incognito window (if applicable)

Hardware

Not Applicable

Connection Type

HTTP

Local or Hosted

https://client.meshtastic.org

Firmware Version

2.7.12

Operating System

macOS 26

Browser

Chrome current

Expected Behavior

On the config->security page there is a section for the new administration system that is supposed to set the security.admin_key array. There are up to 3 keys that can go into this array. The system has no keys there now.

meshtastic --set security.admin_key base64:xxxxx= --set security.admin_key base64:yyyyyy= --set security.admin_key base64:zzzzz=

works just fine, this is just a web client problem.

1. There should not be a generate button for this entry, this makes no sense, as you would never 'generate' a public key for a different node... you need the private key to generate the public key.
2. Setting the key here simply fails.
3. We should be able to set up to 3 keys, not just one.

Actual Behavior

No key is set, no response or feedback.
There is a confusing/useless generate button.

Steps to Reproduce

1. go to config->security
2. try to set an admin key
3. fail
4. notice a generate button that shouldn't be there

Relevant console output

Screenshots

No response

Additional Context

No response

[danditomaso]

@pleasantone Can you test this out on https://client-test.meshtastic.org and let us know if you're seeing the same UI issues? If not will be fixed soon as we're pushing a new release out in the next couple of days.

[pleasantone]

UI looks good, but set did not work.

Please note the meshtastic command for setting the admin keys is different because it is an array, and must take the base64: prefix too.

[danditomaso]

@pleasantone I cant speak to how the CLI works as I dont have very much experience with it. I verified on both Android & IOS meshtastic apps that the Admin key fields dont require a base64: to be prepended to the admin key fields, so in order to maintain feature parity that's how the web client will implement this feature.

[pleasantone]

Yes, I agree the USER should not enter the base64. I was just as a courtesy informing you that the firmware treats these array values as bytes strings, not ascii and that could be the reason that client-test.meshtastic.org is not working properly.

…

On Oct 17, 2025 at 12:37 PM -0700, Dan Ditomaso ***@***.***>, wrote: danditomaso left a comment (meshtastic/web#880) @pleasantone I cant speak to how the CLI works as I dont have very much experience with it. I verified that the Android/Apple Admin key fields dont require a base64: to be prepended to the admin key fields, so in order to maintain feature parity that's how the web client will implement this feature. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>