I solved my issue myself. I don't know if it was the correct way, but it
works. I merely created another portal that has the auto-register option
selected that filters on the SSID of the secure wireless network and
Connection subtype of EAP-TLS.
Thanks,
Keith
From: Keith McCormick <[email protected]>
Sent: Saturday, March 17, 2018 8:14 PM
To: [email protected]
Subject: Still Unregistered after Provisioner completes
Hi,
I cannot apparently figure out how to get certificate provisioning
integrated into the wireless registration process. My desired setup is to
have an open SSID that is bound to the registration network, with a secure
SSID that devices are switched to after successfully authenticating and
gaining a certificate. Currently, I only have AD authentication setup in
the default portal. Registration works from the secure SSID, while no
Provisioner is attached to the default Configuration profile and TTLS is
being used for Radius. If I add a Provisioner and start the registration
process from the open SSID, everything completes through being issued a
certificate and the device is DeAuth'ed and rejoins via the installed
profile. However, the device is still placed in the registration Vlan, as
it is still unregistered. The captive portal comes back up and it is back
to stating that a profile is ready for download and installation. How do I
add a Provisioner to the process and get the device to be in a registered
state? I am testing with an Android device.
Thanks,
Keith
------------------------------------------------------------------------------
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
