So reading this:
https://documentation.meraki.com/MR/Encryption_and_Authentication/Meraki_Local_Authentication_-_MR_8...
I thought, well, let's use OKTA as LDAP for local auth, and so far, after a lot of back and for i was getting communication between Meraki and LDAP
![Screenshot 2023-05-17 at 2.50.08 PM.png Screenshot 2023-05-17 at 2.50.08 PM.png](https://community.meraki.com/t5/image/serverpage/image-id/30165i8C841984E6D4EC90/image-size/medium?v=v2&px=400)
I can get communication on the testing side so clearly Meraki can communicate with OKTA as LDAP on port 389
![Screenshot 2023-05-16 at 4.53.18 PM.png Screenshot 2023-05-16 at 4.53.18 PM.png](https://community.meraki.com/t5/image/serverpage/image-id/30166iAD43CBA58147B3E3/image-size/medium?v=v2&px=400)
Now on site, clearly the AP is not responding to the clients attempting to authenticate:
Client made an 802.1X authentication request to the RADIUS server, but it did not respond.auth_mode='wpa2-802.1x' vlan_id='7' radius_proto='ipv4' radius_ip='127.0.0.1' reason='radius_timeout' radio='1' vap='5' channel='40' rssi='45'
My intention was something like the next:
The AP will accept 802.1x connections, hand it off to 127.0.0.1 for RADIUS and that will then reach out to Okta
Or you feed it a private CA cert to trust, and it will verify the certificates clients hand it.(which i did, using OKTA Certs)
Is this technically possible or I'm just dreaming? Meraki support told me, maybe, then no BUT they sent me to ask OKTA.
I just want to understand why I would need a local Radius Server at all when in theory, the LDAP entity is our OKTA instance and I'm able to connect with Meraki.
Any help will be appreciated.