Thank you again, Heikki. The solution you proposed worked out great.
For the future readers, I ended doing this:
Debug
Identifier ssid-iotd
URL {{ injected }}
TLS_Protocols TLSv1.2
TLS_CAFile /etc/ssl/certs/DigiCert_Assured_ID_Root_CA.pem
HTTP_AuthenticationScheme Basic
HTTP_Username radius
HTTP_
Thank you, Heikki! I will try it out. It looks very flexible. Updating
the documentation will certainly facilitate the usage of this rather
new functionality (the authby being async is a huge win).
CR
Le lun. 20 déc. 2021 à 15:59, Heikki Vatiainen a écrit :
>
> On 18.12.2021 16.05, C R wrote:
>
On 18.12.2021 16.05, C R wrote:
After reading the Radiator documentation and code, it's not completely
clear to me how Radiator determines if a request should is accepted or
rejected by a "AuthBy REST".
There are a couple of ways to do this. Because the AuthBy does not
require a certain respo
Hi,
After reading the Radiator documentation and code, it's not completely
clear to me how Radiator determines if a request should is accepted or
rejected by a "AuthBy REST".
This is the relevant Radiator configuration:
RestAuthRequestDef mac, %{Calling-Station-Id}
RestAuthRequestDef ip, %{NAS-IP
