| Bug #23508 | There is no read-only user category | ||
|---|---|---|---|
| Submitted: | 20 Oct 2006 16:21 | Modified: | 6 Nov 2009 14:52 |
| Reporter: | Shawn Green | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Enterprise Monitor: Web | Severity: | S4 (Feature request) |
| Version: | <= 1.3.0 | OS: | Any (any) |
| Assigned to: | Josh Sled | CPU Architecture: | Any |
| Tags: | account, new, read-only, user | ||
[20 Oct 2006 16:21]
Shawn Green
[5 Oct 2009 11:27]
Andrii Nikitin
See also bug #40450 which requests full ACL support
[4 Nov 2009 15:59]
Enterprise Tools JIRA Robot
Josh Sled writes:
revno: 7626 [merge]
revision-id: jsled@asynchronous.org-20091104154241-a6y469y1fgodbma9
parent: jsled@asynchronous.org-20091103214005-3zfietjemc02fxfv
parent: jsled@asynchronous.org-20090903193522-pdtjn9zamuyyu9g5
committer: Josh Sled <jsled@asynchronous.org>
branch nick: local
timestamp: Wed 2009-11-04 10:42:41 -0500
message:
EM-2256: add support for a "read-only" user role, with conditional quan support and per-struts-action control; add LDAP role-mapping support.
------------------------------------------------------------
[...]
------------------------------------------------------------
revno: 7489.1.1
revision-id: jsled@asynchronous.org-20090903193359-di6gy5rjotaaej4u
parent: eric@mysql.com-20090903143848-t8pcn1v50360hti3
committer: Josh Sled <jsled@asynchronous.org>
branch nick: ro-user
timestamp: Thu 2009-09-03 15:33:59 -0400
message:
RO user as a new role with AuthenticationInterceptor filtering and struts.xml annotation of "ro safety".
[4 Nov 2009 18:21]
Enterprise Tools JIRA Robot
Keith Russell writes: Patch installed in versions => 2.2.0.1523.
[5 Nov 2009 18:20]
Enterprise Tools JIRA Robot
Bill Weber writes: verified the read-only user option added in build 2.2.0.1523
[6 Nov 2009 14:52]
Tony Bedford
An entry has been added to the 2.2.0 changelog:
It was not possible to assign a user a Role that had read-only
permissions.
