
s6t9w (s6t9w) asked a question.
I am trying to configure Okta Linux RADIUS Agent with Cisco Meraki AP and Cisco App in Okta for SSO authentication. The Agent is installed on an AWS Ubuntu instance and I am able to establish connectivity from AP to AWS. When I try to test the authentication, it fails.
Has anyone configured the RADIUS Agent for Meraki AP?

Hello Arjun,
I would love to assist you on your request. Please go ahead and create a support case so this can be tracked properly for a faster resolution. Thank you and have a great day.
Cheers,
Dennis
I have been following with the Okta support team Case 01046502 regarding the same issue.
I involved Cisco Meraki Support on the case, still the same issue. I tried installing the Okta Radius Agent on a Laptop with Ubuntu Server 18.04. The Agent is installed successfully and I assigned the IP address in the same range as Cisco Meraki AP. When tried authenticating, we still see the same problem. The RADIUS test Client is getting a response from Okta RADIUS agent and it is successful. There are no logs in Okta RADIUS agent. We can see the traffic flow in the tcp dumb.
When I use RADIUS Client from Local Laptop. It is authenticating
https://www.iea-software.com/products/radiusnt/radlogin4.cfm
172.16.1.24.58743 > 10.0.1.19.1812: RADIUS, length: 125
Access-Request (1), id: 0x01, Authenticator: 81cfbb6e2dce36576a9dbcb26d727193
User-Name Attribute (1), length: 17, Value: shyams@locus.sh
Acct-Session-Id Attribute (44), length: 17, Value: 1613641124P4czs
NAS-IP-Address Attribute (4), length: 6, Value: 127.0.0.1
NAS-Identifier Attribute (32), length: 11, Value: Localhost
NAS-Port Attribute (5), length: 6, Value: 0
Calling-Station-Id Attribute (31), length: 12, Value: 1115551212
User-Password Attribute (2), length: 18, Value:
Message-Authenticator Attribute (80), length: 18, Value: .ph..j-.D&,.. 4.
09:38:41.066828 IP (tos 0x0, ttl 64, id 49367, offset 0, flags [DF], proto UDP (17), length 74)
10.0.1.19.1812 > 172.16.1.24.58743: RADIUS, length: 46
Access-Accept (2), id: 0x01, Authenticator: e3b5c193640d04ac88ac950d856df95e
Reply-Message Attribute (18), length: 26, Value: Welcome shyams@locus.sh!
When I try from Meraki AP
192.168.128.31.38640 > 10.0.1.19.1812: RADIUS, length: 177
Access-Request (1), id: 0x00, Authenticator: dbd0081f01ff1f79f943e6902e3526fa
User-Name Attribute (1), length: 21, Value: arjunumesh@locus.sh
NAS-IP-Address Attribute (4), length: 6, Value: 6.144.24.112
Calling-Station-Id Attribute (31), length: 19, Value: 02-00-00-00-00-01
Called-Station-Id Attribute (30), length: 25, Value: E0-CB-BC-90-18-70:Locus
Framed-MTU Attribute (12), length: 6, Value: 1400
NAS-Port-Type Attribute (61), length: 6, Value: Wireless - IEEE 802.11
Service-Type Attribute (6), length: 6, Value: Framed
Connect-Info Attribute (77), length: 24, Value: CONNECT 11Mbps 802.11b
EAP-Message Attribute (79), length: 26, Value: .'
Message-Authenticator Attribute (80), length: 18, Value: E...r....en..C.t
09:47:19.762322 IP (tos 0x0, ttl 63, id 25219, offset 0, flags [none], proto UDP (17), length 205)
I was able to resolve the issue. Steps followed.