Cannot submit/change the data using Config Editor

vinoddestiny · **Posted:** Thu Mar 26, 2009 2:26 pm

Hi

I was trying to change the data using a2billing Config Editor found under "System Settings" Menu. Upon clicking "Confirm Data" i got an error

"User: myasterisk does not have access to this feature. Write failed!"

Please advise.

Vino

stavros · **Posted:** Thu Mar 26, 2009 4:47 pm

I would check:
1) permissions on files in /etc/asterisk permit writing by the user/group you run Apache under.
2) your A2B ACL admin login has the relevant permissions enabled
3) A2B's config entries manager_* match the settings specified in /etc/asterisk/manager.conf
Before reporting a problem with v1.4 you should upgrade to the latest svn revision and test again, as the problem may already have been fixed. Also please make it clear which revision you are testing.

bucasia · **Joined:** Mon Mar 02, 2009 8:56 pm **Posts:** 271

Hi, I also see this error on a clean install of v1.3.4

(I know this is a 1.4 bug report forum but figured this might be relevant)

On checking in the file A2Billing_UI/Public/phpconfig_init.php it appears as though there is some sort of hard coded user in there -

Code:

// Since login screen is still in the works, fake
// the user has logged in with success for the prototype.
// for write access $fakeuser must exist in $access_file
$fakeuser = "myasterisk";

In my case changing the $fakeuser to "admin" fixed the problem.

Is this something that's left over that still needs to be hard coded in there?

Matt

stavros · **Posted:** Thu Apr 16, 2009 5:00 pm

bucasia wrote:

In my case changing the $fakeuser to "admin" fixed the problem.

I'm certain this was purely co-incidence, and some other change you made actually fixed it. If you read the remainder of the phpconfig*.php files you can see that the values of $_SESSION['valid_user'] or $fakeuser are never used in any meaningful way; authentication is instead handled by A2B's framework, so it's no longer needed.

bucasia · **Joined:** Mon Mar 02, 2009 8:56 pm **Posts:** 271

That's weird. I will double check and confirm but I'm pretty sure it was this change that fixed it.

(I tested on 2 separate systems earlier when I did this - although admittedly I installed both so maybe there's something peculiar to my install routine)

Added after 22 minutes:

Yes, strange. Editing the $fakeuser setting does enable/disable updating the /etc/asterisk/a2billing.conf file through the admin interface for me.

For instance if I change -

Code:

$fakeuser = "admin1";

I get the following error when clicking on Update

Code:

User: admin1 does not have access to this feature.
Write failed!

Not a problem at all if it doesn't affect anyone else as I can work around it.

The only thing I can think that I do with users when I install that could be causing this is deleting the 'root' user from the admin interface? I can't see why though.

Matt

princemasud · **Joined:** Wed Apr 29, 2009 8:02 pm **Posts:** 3

This bug is not fixed yet in the latest revision,i had the same problem with latest version

jroper · **Joined:** Fri Jun 23, 2006 3:56 pm **Posts:** 4065

This is almost certainly a matter for installation, not A2Billing.

For interest, what user is running apache, and what user is running Asterisk?

Joe

provided by Star2Billing S.L.

Cannot submit/change the data using Config Editor

Who is online