I asked about this earlier, but I wanted to double-check after doing more testing.
I've successfully set up separate self-registration portals for our different user groups by putting the second portal on a separate interface, and setting up a connection profile that filters on the FQDN of the secondary portal. When I do that, the second portal successfully presents the device role list that's specified in the secondary connection profile instead of the default. However, it doesn't matter what I set the authentication source to on the secondary connection profile -- that portal will always use the authentication source of the default connection profile instead. Is this how things are supposed to work, or is this a bug? It's very close to being what I need, but if the two portals always use the same authentication source, there's no point to having more than one. Thanks. _______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
