The self registration portal are per Connection Profile basis. As long you have a different URI to reach it or source you should be able to display different one.
The default URI are https://pf.domain.com/status <https://pf.domain.com/status> and https://pf.domain.com/device-registration <https://pf.domain.com/device-registration> It’s a known issue that we do have problems displaying multiple ones. It needs to be tested in your case. Thanks, Ludovic Zammit Product Support Engineer Principal Cell: +1.613.670.8432 Akamai Technologies - Inverse 145 Broadway Cambridge, MA 02142 Connect with Us: <https://community.akamai.com/> <http://blogs.akamai.com/> <https://twitter.com/akamai> <http://www.facebook.com/AkamaiTechnologies> <http://www.linkedin.com/company/akamai-technologies> <http://www.youtube.com/user/akamaitechnologies?feature=results_main> > On Feb 15, 2022, at 9:31 AM, Toren Smith via PacketFence-users > <packetfence-users@lists.sourceforge.net> wrote: > > Does the portal module customization affect the self-registration > portal? The documentation only talks about using it for the captive > portal, which I'm not using. > > Is it possible to just have two separate self-registration portals? > I'm fine with people having to go to separate URLs to register things. > > On Tue, Feb 15, 2022 at 8:48 AM Diego Garcia del Rio <garc...@gmail.com > <mailto:garc...@gmail.com>> wrote: >> >> you could create two authentication sources (both pointing to the same >> LDAP), one which filters faculty and another students.(you would have to >> play with the LDAP filters so that the user is not even found if it you >> search for faculty using the student's authentication source) >> and then you could present two different "login options" -> faculty login >> (which only uses the faculty LDAP as authentication source) and student >> login(which only uses the student LDAP as auth source), each which leads to >> the the two different "select-role" portal modules, one tuned for faculty >> and the other for staff >> >> it its only 2 "paths" then its probably ok... otherwise, it could become a >> bit un-manageable >> >> >> On Tue, Feb 15, 2022 at 8:03 AM Toren Smith via PacketFence-users >> <packetfence-users@lists.sourceforge.net> wrote: >>> >>> I'm not sure what the right approach is for this, or how much of this >>> PacketFence can do. I'm not planning on using PF as a captive portal, >>> I just want to use it for the self-service device registration page >>> for MAB on wired and wireless connections. Ideally what I wanted was a >>> system where our faculty or students could sign in to the portal and >>> register their devices and select from a couple of different roles for >>> each device. I can authenticate the accounts via AD or LDAP just fine, >>> and I can assign roles to the users based on LDAP attributes. If I >>> don't specify a list of roles for the Self-Service Portal, it'll >>> assign the student/faculty role to the device when it's registered, >>> but if I put in a list of roles they can choose from, then *all* users >>> can choose from any of those, regardless of the user's role. >>> >>> So what I want is for students to sign into the Portal and get the >>> option of registering their devices in role A or role B, while faculty >>> signing in get to choose between roles C or D. But right now if I >>> leave the list blank, neither of them gets to choose a role for their >>> devices, and if I put the list of these in, they can all chose from A, >>> B, C, or D. >>> >>> I'd be fine with having two separate portal pages for the two groups, >>> but I don't see an obvious way of doing that. I've read through all >>> the documentation, but it didn't seem to cover these cases. >>> >>> Does anybody know the answer? Thanks. >>> >>> >>> _______________________________________________ >>> PacketFence-users mailing list >>> PacketFence-users@lists.sourceforge.net >>> https://urldefense.com/v3/__https://lists.sourceforge.net/lists/listinfo/packetfence-users__;!!GjvTz_vk!EJK5_O3kHtaYO-iN3tqu6GQbMaWfFePEGrxSAoKKeJRfjsoRJFzBZ53_JcpHSMIC$ >>> >>> <https://urldefense.com/v3/__https://lists.sourceforge.net/lists/listinfo/packetfence-users__;!!GjvTz_vk!EJK5_O3kHtaYO-iN3tqu6GQbMaWfFePEGrxSAoKKeJRfjsoRJFzBZ53_JcpHSMIC$> >>> > > > _______________________________________________ > PacketFence-users mailing list > PacketFence-users@lists.sourceforge.net > <mailto:PacketFence-users@lists.sourceforge.net> > https://urldefense.com/v3/__https://lists.sourceforge.net/lists/listinfo/packetfence-users__;!!GjvTz_vk!EJK5_O3kHtaYO-iN3tqu6GQbMaWfFePEGrxSAoKKeJRfjsoRJFzBZ53_JcpHSMIC$ > > <https://urldefense.com/v3/__https://lists.sourceforge.net/lists/listinfo/packetfence-users__;!!GjvTz_vk!EJK5_O3kHtaYO-iN3tqu6GQbMaWfFePEGrxSAoKKeJRfjsoRJFzBZ53_JcpHSMIC$>
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
