Hi guys, sorry for the necroposting: is this issue fixed with the new
realm strip options in 8.0?
Or it is for a different thing?
Thanks
Il 19/10/2017 16:42, Fabrice Durand via PacketFence-users ha scritto:
Hello Cristian,
btw it's in the road map.
Regards
Fabrice
Le 2017-10-19 à
Hello Cristian,
btw it's in the road map.
Regards
Fabrice
Le 2017-10-19 à 05:31, Cristian Mammoli via PacketFence-users a écrit :
> Hello Fabrice, thanks. I was afraid I was doing something wrong.
> I could possibly play with "radius-server domain-stripping" option on
> IOS switches but I
Hello Fabrice, thanks. I was afraid I was doing something wrong.
I could possibly play with "radius-server domain-stripping" option on
IOS switches but I agree this should be handled by PF.
Il 18/10/2017 17:22, Fabrice Durand via PacketFence-users ha scritto:
Hello Cristian,
It is but
Hello Cristian,
It is but because the supplicant send DOMAIN\Username and the portal use
the sAMAccountName.
The solution could be to use another attribute that contain the
DOMAIN\Username but i am not sure it exist on the active directory and i
am not sure that user will be happy to fill
Hi, sorry to dig this up... Could someone please explain if this
behaviour is expected or not?
Thank you
Il 02/08/2017 17:59, Cristian Mammoli via PacketFence-users ha scritto:
Of course I checked "Use stripped username" and added "strip to the
realm option.
Il 02/08/2017 15:26, Cristian
Of course I checked "Use stripped username" and added "strip to the
realm option.
Il 02/08/2017 15:26, Cristian Mammoli via PacketFence-users ha scritto:
Hi, in my POC I'm trying the following setup:
If a computer does not support 802.1x should be presented with the
captive portal where the
Hi, in my POC I'm trying the following setup:
If a computer does not support 802.1x should be presented with the
captive portal where the user can register the device, access the
production network and join the domain
Once joined 802.1x is configured and enabled via GPO.
With 802.1x enabled
