PacketFence
Bug Tracking System

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001641PacketFencecorepublic2013-05-10 18:082013-07-11 08:44
Reporterlmunro 
Assigned Tofrancis 
PrioritynormalSeverityminorReproducibilitysometimes
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version4.0.0 
Target VersionFixed in Version4.0.1 
Summary0001641: max nodes per-user limit reached for admin user
DescriptionA user reports:
I've been doing some work on our PF 4.0 install. I have LDAP
authentication working for the admin logins as well as logging in via
RADIUS. I believe we talked yesterday about the "User Sources" being
used for identifying user roles when authenticating via 802.1x.
Looking at the vlan.pm code, this appears to be what will happen, but
I need to have the node in a registered state first. So how do we go
about doing that?

    Additionally, if I try to manually switch the node to Registered, I
get the following in the logs :

INFO: per-category max nodes per-user limit reached: 1 are already
registered to admin for category
Additional Informationnode:is_max_reg_nodes_reached tests if $pid equals $default_pid.
$default_pid is defined as 1 in config.pm whereas it is entered as "admin" in the database.

Should that be changed?
TagsNo tags attached.
fixed in git revision
fixed in mtn revision
Attached Files

- Relationships

-  Notes
(0003303)
francis (administrator)
2013-05-14 12:46

I fixed the value of $default_pid :

https://github.com/inverse-inc/packetfence/commit/d8d6c5f65ca68d4c9622d15e76bc54ac3c64bf39 [^]

- Issue History
Date Modified Username Field Change
2013-05-10 18:08 lmunro New Issue
2013-05-14 12:46 francis Note Added: 0003303
2013-07-11 08:44 francis Status new => resolved
2013-07-11 08:44 francis Fixed in Version => 4.0.1
2013-07-11 08:44 francis Resolution open => fixed
2013-07-11 08:44 francis Assigned To => francis


Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker