|
From: Christian M. <cmc...@gr...> - 2020-02-03 20:37:51
|
So I guess I'm not understanding a fundamental concept in PacketFence... I ended up moving this new authentication source up to the highest priority and admin portal authentication started working. So, I'm guessing authentication sources operate on a first-match basis? Meaning, that if I had an authentication source that matched the user but *didn't apply* an administration access level at say priority 1, any additional authentication sources scoped to the same Base DN with matches would be ignored? On Mon, Feb 3, 2020 at 3:05 PM Christian McDonald <cmc...@gr...> wrote: > I've got a simple internal authentication source for logging into the > admin portal via AD group membership. When I run ./pftest I get the > following: > > Authenticating against 'SYS_PacketFence_Admin' in context 'portal' > Authentication SUCCEEDED against SYS_PacketFence_Admin (Authentication > successful.) > Did not match against SYS_PacketFence_Admin for 'authentication' rules > Matched against SYS_PacketFence_Admin for 'administration' rule > SYS_PacketFence_Admin > set_access_level : ALL > > However, when I try logging into the admin portal, I get "Wasn't able to > authenticate those credentials." > > Any ideas? > -- R. Christian McDonald *Director of Technology* Grand Rapids Adventist Acadmey T: (888) 791-3108 (x1105) O: (616) 791-9797 (x1105) C: (616) 856-9291 1151 Oakeigh Road NW Grand Rapids, MI 49504 |