Anyway to call the secret from incoming auth request with the raw module, like %{raw:secret}?
On 14 Dec 2014, at 23:04, Eric Geier <egeier@onspottechs.com> wrote:
Anyway to call the secret from incoming auth request with the raw module, like %{raw:secret}?
What's the 'raw' module? You can get the secret configured for the client the request appeared to come from using "%{client:secret}". -Arran Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS development team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
Thanks, Arran. Here's a link discussing the raw module: http://www.radiusdesk.com/getting_started/install_ubuntu_freeradius I will try what you gave, On Mon, Dec 15, 2014 at 12:06 AM, Arran Cudbard-Bell <a.cudbardb@freeradius.org> wrote:
On 14 Dec 2014, at 23:04, Eric Geier <egeier@onspottechs.com> wrote:
Anyway to call the secret from incoming auth request with the raw module, like %{raw:secret}?
What's the 'raw' module?
You can get the secret configured for the client the request appeared to come from using "%{client:secret}".
-Arran
Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS development team
FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Anyway to use "%{client:secret}" inside the Secret, in clients.conf? Tried and doesn't appear to work. On Mon, Dec 15, 2014 at 12:06 AM, Arran Cudbard-Bell <a.cudbardb@freeradius.org> wrote:
On 14 Dec 2014, at 23:04, Eric Geier <egeier@onspottechs.com> wrote:
Anyway to call the secret from incoming auth request with the raw module, like %{raw:secret}?
What's the 'raw' module?
You can get the secret configured for the client the request appeared to come from using "%{client:secret}".
-Arran
Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS development team
FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Dec 15, 2014, at 10:47 AM, Eric Geier <egeier@onspottechs.com> wrote:
Anyway to use "%{client:secret}" inside the Secret, in clients.conf? Tried and doesn't appear to work.
You can’t set the secret by looking at the secret. What are you trying to do? Ask about that, rather than about why a particular solution doesn’t work. I have no idea what the *problem* is. Alan DeKok.
Hi,
Anyway to use "%{client:secret}" inside the Secret, in clients.conf? Tried and doesn't appear to work.
You can’t set the secret by looking at the secret.
What are you trying to do? Ask about that, rather than about why a particular solution doesn’t work. I have no idea what the *problem* is.
i'm guessing he wants to read the secret that the RADIUS client actually sent in the packet and then use that for the client statement - in which case there is confusion as the client doesnt send secret in the datagram :/ alan
On 15 Dec 2014, at 11:44, A.L.M.Buxey@lboro.ac.uk wrote:
Hi,
Anyway to use "%{client:secret}" inside the Secret, in clients.conf? Tried and doesn't appear to work.
You can’t set the secret by looking at the secret.
What are you trying to do? Ask about that, rather than about why a particular solution doesn’t work. I have no idea what the *problem* is.
i'm guessing he wants to read the secret that the RADIUS client actually sent in the packet and then use that for the client statement - in which case there is confusion as the client doesnt send secret in the datagram :/
Um yes, else it wouldn't be very secret would it. Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS development team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
On Dec 14, 2014, at 11:04 PM, Eric Geier <egeier@onspottechs.com> wrote:
Anyway to call the secret from incoming auth request with the raw module, like %{raw:secret}?
The “raw” module isn’t distributed with the server, for a number of good reasons. The intention behind the “raw” module is to use it when you have dynamic clients. i.e. when no secret exists for the client. The attribute contents are used to look the secret up in a database. So that’s how you get the secret. Alan DeKok.
participants (4)
-
A.L.M.Buxey＠lboro.ac.uk -
Alan DeKok -
Arran Cudbard-Bell -
Eric Geier