Local status - Unable to set password

[MelvinMagnehag]

Hello everyone,
 
Since the update of the Network Wide -> General -> Device Configuration -> Login Credentials, i've noticed that you are unable to set an password for the local status of an MX.
Looks like the the code for the HTML is missing a Value/Name for the placeholder form which in turn leads to the password never being saved in the Meraki Dashboard.

We've also noticed that for networks that have had an password before, that password no longer exist and you cannot login into the local status page.

The fix/workaround that we have been using is to create an new network and not setting a password for the local status page, then the network defaults to the serialnumber of the device.

Have any of you guys also seen this problem and how did you fix it?

[jimmyt234]

Yes - we have experienced the same across multiple Orgs and have used the same workaround as you have already discovered.

Ticket logged with support since 21st May and no meaningful update since then other than: "This is a known issue that our Development Team is still investigating and working on a fix in the new page so you can see the Password"

[Boomerang94]

While I can’t share internal backend details around the bug, I can tell you that the issue relates to how the dashboard server communicates with the local device. During this interaction, the password delivered to the Meraki device by the dashboard appears to become 'corrupted', which leads to the problem you're seeing. As you already know, a workaround is available, and I can assure you that our team is actively prioritising a permanent fix.

[jimmyt234]

Does make you wonder how this was not caught during QA of the change in Dev/UAT environments 🙂

[harmankardon]

@Boomerang94 Can you give any indication of timeline for this fix?

[harmankardon]

Can you give some more details on how you are using the workaround you mentioned? Are you essentially recreating the network, moving devices over to the new network and then deleting the old network?

I've been fighting with this local device credentials issue thinking it was a browser issue on my end, extremely frustrating. I don't even know what the local password is now for several of my networks.

[MelvinMagnehag]

Hello,

You need to create an entirely new network, you can make changes to this new network but be careful so you don't give it an password to the local status page. This will revert you devices on the network to use the serialnumber as the login.

Alternative is to reset the devices, don't give them an uplink to reach the Meraki Dashboard and then you are able to also use the serialnumber as the login.

Those are the ways i've found worked for me!

[cmr]

I can't believe that it has been almost a month and this still isn't fixed!  Did someone find a vulnerability that hasn't been disclosed yet, as I cannot think of another reason why the issue should persist for this long...?

[jimmyt234 · Accepted solution]

Our recent support interaction led us to this update: "I can confirm, that the feature does work and you can set and change credentials as normal, you just need to make a note of them as once they are saved they don't appear in the UI for you to view if needed. The issue is purely cosmetic."

I can confirm I have tried this a couple of times and it has worked.

[MelvinMagnehag]

Thank you for the update jimmyt234, i've just tried the way that the Meraki Support updated you on and i can also confirm that this way works.

[whargrove]

Hey jimmyt234, which firmware version are you using?

[jimmyt234]

I have tried this on both 18.211.x and 19.1.8 versions.

[whargrove]

Meraki support confirmed that they are treating this as a high priority bug.  On the MX, they confirmed it affects 18.211.5 and several previous versions.  I'm on 18.211.6 and I'm seeing the issue.  The workarounds provided were to upgrade to stable release candidate 19.1.8.1, or disconnect the WAN interface and factory reset the MX.  The factory reset is only a temporary solution, since once the MX connects to the cloud, the corrupt password will get applied to the device again.