Open Source Training Seminar FreePBX Paid Support

Ticket #684 (closed Bugs: worksforme)

Opened 2 years ago

Last modified 2 years ago

cannot add administrator after you have added users into the system

Reported by: anonymous Assigned to:
Priority: blocker Milestone:
Component: Applications Module Version: 2.0.1
Keywords: auth db users Cc:
Confirmation: SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description

After adding users into the system I decided to use the included db user names to control access. I get this error AUTHTYPE is not set to 'database' in /etc/amportal.conf - Module crippled. If I add this to the conf I am locked out since I have not set a user to access the web interface only phone users.

This bug is causing me to only use http auth and cannot enable the db auth.

Change History

04/25/06 11:01:09 changed by RyanCourtnage

  • status changed from new to closed.
  • resolution set to invalid.

Create an admin user while AUTHTYPE=none. Then login with that user after setting AUTHTYPE=database (use a blank password).

04/27/06 14:07:38 changed by ap0ught

  • status changed from closed to reopened.
  • resolution deleted.

I have tried that fix and it is not working. I submitted the bug from this looking at this page they describe the same bug I have above

http://aussievoip.com.au/wiki/index.php?page=freePBX-Admin

If you already have users in the system you cannot create a new admin user

please advise

04/27/06 14:57:02 changed by RyanCourtnage

Are you certain you don't have directory security enabled for the freepbx webroot in httpd.conf?

I can't duplicate your problem.

(follow-up: ↓ 9 ) 04/29/06 14:46:26 changed by skirmish

I just fix that problem. It is simple like that. Disable db auth in the config. Go to the web. Create one account, let's say "test" and give full rights to it. Enable db auth and try to login with user test with no passowrd. Then go and delete admin user from the web interface and set password to test account. This worked with me.

05/01/06 07:35:04 changed by RyanCourtnage

  • status changed from reopened to closed.
  • resolution set to invalid.

05/01/06 10:23:13 changed by ap0ught

  • status changed from closed to reopened.
  • resolution deleted.

what version of software were you testing this with. I might have installed free pbx before you fixed this bug.

05/03/06 11:38:59 changed by RyanCourtnage

IMO, this bug report should be closed. What's the remaining issue?

FYI - you cannot have directory security set in Apache's httpd.conf at the dame time as using authtype=database.

05/05/06 09:06:47 changed by RyanCourtnage

  • status changed from reopened to closed.
  • resolution set to worksforme.

(in reply to: ↑ 4 ) 09/08/06 10:28:19 changed by Nutster

Replying to skirmish: What I did is: Remove all administrators created when AUTHTYPE=none. Open up etc/amportal.conf and change the AUTHTYPE to database. Find the user name and password that is in there (Look for AMPDBUSER and AMPDBPASS). I restart the http server (service httpd restart) and then try logging in using the aformentioned name and password. After that I create an 'admin' user with full permissions which I use to build my restricted users.

The link given about is a great resource. Helped me learn what the Administrators module is and how to use it.

Donate



Support
Download
Develop
Forums
News
Documentation
Paid Support
About

Paid Ads