[horde] Getting there but not quite... part deux

Eric spamsink at scoot.netis.com
Sun Nov 5 10:33:51 PST 2006


At 01:17 AM 11/5/2006, Ben Chavet wrote:


>There is a script in horde/scripts/sql/script.initial_horde_user.sql which 
>will add a user to your newly configured sql authentication 
>backend.  username: admin password: admin (which should be changed as soon 
>as you get logged in).
>
>The reason you are not able to log in is probably due to the fact that you 
>have no users defined in your horde_users table (which is what this script 
>takes care of).
>
>Also, in order for this user to be an admin, you should edit horde's 
>config.php and add 'admin' to the array of admin users to look something 
>like: $conf['auth']['admins'] = array('admin');


Good afternoon, Ben.

Thanks, that did it!  :-)

Now, in the horde setups under the Database tab, should "User to connect to 
the database as" also be "admin" with a password of "admin"?

I currently have the "User to connect to the database as" set to the 
"NewHordeUser" user I created in MySQL, with its password.  To create the 
"NewHordeUser" user I logged into MySQL and said:

GRANT ALL PRIVILEGES ON *.* TO 'NewHordeUser'@'%' IDENTIFIED BY 'some_pass' 
WITH GRANT OPTION;

Was that the right thing to do?

I'm also still slightly fuzzy on whether I should have said

GRANT ALL PRIVILEGES ON *.* TO 'NewHordeUser'@'%'...

...or...

GRANT ALL PRIVILEGES ON *.* TO 'NewHordeUser'@'TheHostName'...

(... a little confused on the differences between "%" and the host name, 
under MySQL, though I know they're different...)

Thanks...





More information about the horde mailing list