Hello Diogo,
for that you need to configure freeradius to forward the request to the
nps server and create a connection profile with a filter on the ssid
with auto register.
Nothing really complicate to configure in PacketFence.
In order to help you to configure freeradius to proxy the request to the
nps you can apply this PR:
cd /usr/local/pf
curl
https://patch-diff.githubusercontent.com/raw/inverse-inc/packetfence/pull/3278.diff|patch
-p1
mv conf/radiusd/proxy.conf.inc.example conf/radiusd/proxy.conf.inc
And read that:
https://github.com/inverse-inc/packetfence/pull/3278/files#diff-753fbb0c241226a070b013b0778ed088
Regards
Fabrice
Le 2018-07-10 à 10:33, Diogo Rocha via PacketFence-users a écrit :
Hi All.
I wish you´re fine.
There´s any way to make PF just forward radius authenticantion on
portal without configure AD?
My ideia.
Portal have 2 options for authentication.
1 - Guest – all OK, registering with sponsor.
2 – Domain user – i Thought that maybe was possible to PF just send
username and password with radius authentication (1812). And My radius
server (NPS) work on authorization and reply message for PF with OK.
It seems like a by-pass radius.
Its possible?
To make the portal accepts 802.1x, i have to configure AD with a
domain user? Its only option?
Tks again and best regards.
Diogo Rocha
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
