topic Re: RADIUS Server secret is not correct when adding via API in Network Platform API

RADIUS Server secret is not correct when adding via API

bhilgenkamp2023 — Wed, 14 Feb 2024 15:18:16 GMT

I'm pushing switch access policies using:

https://api.meraki.com/api/v1/networks/{networkId}/switch/accessPolicies

Everything looks great on the dashboard after I add them except for the RADIUS secret that shows when I click the "Show" button on the dashboard. The secret that is shown is incorrect, and is the same every time even when I change the secret I'm sending via API. Example of my payload:

"radiusServers": [
    {
        "host": "1.1.1.1",
        "port": 1812,
        "secret": "secretcode"
    },
    {
        "host": "2.2.2.2",
        "port": 1812,
        "secret": "acompletelydifferentsecretcode"
    }

In the above example, both of the secrets would appear as the same in the dashboard. Am I doing something wrong here or is this an issue with the API?

Re: RADIUS Server secret is not correct when adding via API

Raphael_L — Wed, 14 Feb 2024 15:42:19 GMT

when I click the "Show" button on the dashboard

You can't show the shared secret on the dashboard. What are you refering to ?

Re: RADIUS Server secret is not correct when adding via API

bhilgenkamp2023 — Wed, 14 Feb 2024 16:54:46 GMT

I have the option to show the secret on the servers on my Access Policies pages:

Re: RADIUS Server secret is not correct when adding via API

ww^ — Wed, 14 Feb 2024 17:28:59 GMT

It never shows the real secret even if you add it from the dashboard itself. Its always the same "fake" secret. But the real one you entered should be used

Re: RADIUS Server secret is not correct when adding via API

bhilgenkamp2023 — Wed, 14 Feb 2024 17:41:29 GMT

Interesting. Good to know - not sure why the "show" option is even there if it won't actually show it. I suppose just for confirmation when entering it. Thanks!

Re: RADIUS Server secret is not correct when adding via API

Raphael_L — Wed, 14 Feb 2024 17:58:42 GMT

And that UI is only present because you enabled Org-Wide Radius server which is a feature currently in Early-Access.

EDIT : I had already "flagged" this via : https://community.meraki.com/t5/Dashboard-Administration/Org-level-RADIUS-Server-Open-discussion/m-p/214190