Mysql User management

[Lord Asriel]

I'm a newbie in mysql and I've a question about user definition in
Mysql.
According to informations collected from manuals I believed that a
user definition specifying host="%" on mysql server 'A' granted me
connection from whatever client (with command "mysql -hA -uuser -p");
but executing that command from server, to say, 'B', mysql denies
access to user@B. The matter can be solved defining a new user with
host B (it's to say user@B), but, in that case what's the meaning of a
generic user@%?
Thanks
Andrea Paventi

[Andrew DeFaria]

Lord Asriel wrote:

I'm a newbie in mysql and I've a question about user definition in
Mysql. According to informations collected from manuals I believed
that a user definition specifying host="%" on mysql server 'A' granted
me connection from whatever client (with command "mysql -hA -uuser
-p"); but executing that command from server, to say, 'B', mysql
denies access to user@B. The matter can be solved defining a new user
with host B (it's to say user@B), but, in that case what's the meaning
of a generic user@%?

I've been bothered by the same behavior even though
http://www.mysql.com/doc/en/GRANT.html seems to imply that it is doable:

In order to accommodate granting rights to users from arbitrary
hosts, MySQL supports specifying the |user_name| value in the form
|user@host|. If you want to specify a |user| string containing
special characters (such as `-'), or a |host| string containing
special characters or wildcard characters (such as `%'), you can
quote the user or host name (for example,
|'test-user'@'test-hostname'|).

You can specify wildcards in the hostname. For example,
|user@'%.loc.go v'| applies to |user| for any host in the |loc.gov|
domain, and |user@'144.155. 166.%'| applies to |user| for any host in
the |144.155.166| class C subnet.

The simple form |user| is a synonym for |user@"%"|.

Don't know why it doesn't work for you and me.
--
I have seen the truth and it makes no sense.

[Andrew DeFaria]

Lord Asriel wrote:

I'm a newbie in mysql and I've a question about user definition in
Mysql. According to informations collected from manuals I believed
that a user definition specifying host="%" on mysql server 'A' granted
me connection from whatever client (with command "mysql -hA -uuser
-p"); but executing that command from server, to say, 'B', mysql
denies access to user@B. The matter can be solved defining a new user
with host B (it's to say user@B), but, in that case what's the meaning
of a generic user@%?

I've been bothered by the same behavior even though
http://www.mysql.com/doc/en/GRANT.html seems to imply that it is doable:

In order to accommodate granting rights to users from arbitrary
hosts, MySQL supports specifying the |user_name| value in the form
|user@host|. If you want to specify a |user| string containing
special characters (such as `-'), or a |host| string containing
special characters or wildcard characters (such as `%'), you can
quote the user or host name (for example,
|'test-user'@'test-hostname'|).

You can specify wildcards in the hostname. For example,
|user@'%.loc.go v'| applies to |user| for any host in the |loc.gov|
domain, and |user@'144.155. 166.%'| applies to |user| for any host in
the |144.155.166| class C subnet.

The simple form |user| is a synonym for |user@"%"|.

Don't know why it doesn't work for you and me.
--
I have seen the truth and it makes no sense.

[Andrew DeFaria]

Lord Asriel wrote:

I'm a newbie in mysql and I've a question about user definition in
Mysql. According to informations collected from manuals I believed
that a user definition specifying host="%" on mysql server 'A' granted
me connection from whatever client (with command "mysql -hA -uuser
-p"); but executing that command from server, to say, 'B', mysql
denies access to user@B. The matter can be solved defining a new user
with host B (it's to say user@B), but, in that case what's the meaning
of a generic user@%?

I've been bothered by the same behavior even though
http://www.mysql.com/doc/en/GRANT.html seems to imply that it is doable:

In order to accommodate granting rights to users from arbitrary
hosts, MySQL supports specifying the |user_name| value in the form
|user@host|. If you want to specify a |user| string containing
special characters (such as `-'), or a |host| string containing
special characters or wildcard characters (such as `%'), you can
quote the user or host name (for example,
|'test-user'@'test-hostname'|).

You can specify wildcards in the hostname. For example,
|user@'%.loc.go v'| applies to |user| for any host in the |loc.gov|
domain, and |user@'144.155. 166.%'| applies to |user| for any host in
the |144.155.166| class C subnet.

The simple form |user| is a synonym for |user@"%"|.

Don't know why it doesn't work for you and me.
--
I have seen the truth and it makes no sense.

[Lord Asriel]

>

I've been bothered by the same behavior even though
http://www.mysql.com/doc/en/GRANT.html seems to imply that it is doable:

In order to accommodate granting rights to users from arbitrary
hosts, MySQL supports specifying the |user_name| value in the form
|user@host|. If you want to specify a |user| string containing
special characters (such as `-'), or a |host| string containing
special characters or wildcard characters (such as `%'), you can
quote the user or host name (for example,
|'test-user'@'test-hostname'|).

You can specify wildcards in the hostname. For example,
|user@'%.loc.go v'| applies to |user| for any host in the |loc.gov|
domain, and |user@'144.155. 166.%'| applies to |user| for any host in
the |144.155.166| class C subnet.

The simple form |user| is a synonym for |user@"%"|.

Don't know why it doesn't work for you and me.

Thanks for your answer even though it doesn't solve the problem it
gives me a hint: I'm going to try defining a "user@%.mydomai n.it";
let's see if it works

Andrea Paventi

[Lord Asriel]

>

I've been bothered by the same behavior even though
http://www.mysql.com/doc/en/GRANT.html seems to imply that it is doable:

In order to accommodate granting rights to users from arbitrary
hosts, MySQL supports specifying the |user_name| value in the form
|user@host|. If you want to specify a |user| string containing
special characters (such as `-'), or a |host| string containing
special characters or wildcard characters (such as `%'), you can
quote the user or host name (for example,
|'test-user'@'test-hostname'|).

You can specify wildcards in the hostname. For example,
|user@'%.loc.go v'| applies to |user| for any host in the |loc.gov|
domain, and |user@'144.155. 166.%'| applies to |user| for any host in
the |144.155.166| class C subnet.

The simple form |user| is a synonym for |user@"%"|.

Don't know why it doesn't work for you and me.

Thanks for your answer even though it doesn't solve the problem it
gives me a hint: I'm going to try defining a "user@%.mydomai n.it";
let's see if it works

Andrea Paventi

[Lord Asriel]

>

I've been bothered by the same behavior even though
http://www.mysql.com/doc/en/GRANT.html seems to imply that it is doable:

In order to accommodate granting rights to users from arbitrary
hosts, MySQL supports specifying the |user_name| value in the form
|user@host|. If you want to specify a |user| string containing
special characters (such as `-'), or a |host| string containing
special characters or wildcard characters (such as `%'), you can
quote the user or host name (for example,
|'test-user'@'test-hostname'|).

You can specify wildcards in the hostname. For example,
|user@'%.loc.go v'| applies to |user| for any host in the |loc.gov|
domain, and |user@'144.155. 166.%'| applies to |user| for any host in
the |144.155.166| class C subnet.

The simple form |user| is a synonym for |user@"%"|.

Don't know why it doesn't work for you and me.

Thanks for your answer even though it doesn't solve the problem it
gives me a hint: I'm going to try defining a "user@%.mydomai n.it";
let's see if it works

Andrea Paventi