Project

General

Profile

Actions
Copy link

Bug #2366

closed

Error in User Manager - Privileges are not being enforced

Added by Stephen Groat about 13 years ago. Updated over 10 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
User Manager / Privileges
Target version:
-
Start date:
04/10/2012
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0.1
Affected Architecture:
amd64

Description

After adding a user and granting that user all privileges (both by adding to admin group and manually selecting all privileges), the user is allowed to log in but get 201 error.

Through ssh, user does not get pfSense prompt, direct towards shell.

Installed packages:

nmap
Open-VM-Tools (non-beta version)

Files

Download all files
Screen Shot 2012-04-10 at 11.05.01 PM.png (200 KB) Screen Shot 2012-04-10 at 11.05.01 PM.png Screenshot 1 Stephen Groat, 04/10/2012 11:05 PM
Screen Shot 2012-04-10 at 11.06.38 PM.png (156 KB) Screen Shot 2012-04-10 at 11.06.38 PM.png Screenshot 2 Stephen Groat, 04/10/2012 11:05 PM
Screen Shot 2012-04-10 at 11.06.43 PM.png (73.1 KB) Screen Shot 2012-04-10 at 11.06.43 PM.png Screenshot 3 Stephen Groat, 04/10/2012 11:05 PM
Screen Shot 2012-04-10 at 11.07.48 PM.png (266 KB) Screen Shot 2012-04-10 at 11.07.48 PM.png Screenshot 4 Stephen Groat, 04/10/2012 11:05 PM
config-purple.cirt.vt.edu-20120410230924.xml (23 KB) config-purple.cirt.vt.edu-20120410230924.xml Config with passwords redacted Stephen Groat, 04/10/2012 11:05 PM
Actions
Copy link
 #1

Updated by Chris Buechler about 13 years ago

  • Status changed from New to Rejected

not a legit bug report. the CLI behavior is expected, and assigning privileges as described works. no idea what a "201 error" would be or come from, post to the forum or list for help including details of "201 error".

Actions
Copy link
 #3

Updated by Adam Esslinger over 10 years ago

I have also experienced this bug. When pfsense is set to use LDAP as the authentication server (specifically Active Directory) and a user either LDAP or local DB logs in and creates a new user the permissions aren't really applied, however the web GUI shows the permissions as applied. When you logout after account creation and login as the new user you will get an error 201 page. If you log back in and set the authentication back to local DB and create a new user the permissions are correctly applied on the new user. Im using 2.1.5-RELEASE (amd64)

Actions
Copy link
 #4

Updated by Ermal Luçi over 10 years ago

You should follow setup procedures for AD.
Search the net and you will find them.

Actions
Copy link

Also available in: Atom PDF