Task #548 (closed)
Opened 17 years ago
Closed 17 years ago
Create default group to ease install
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Milestone: | 3.0-Beta1 |
| Component: | Deployment | Version: | 3.0-M3 |
| Keywords: | REVIEW | Cc: | cxallan, dzmacdonald |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
For milestone:3.0-Beta1, it would be nice to have a default group added so that installs are easier (Admin are not required to create a group just in order to create a user).
For the long run, we'll need to decide on a user/group policy (perhaps choosable per install):
- "default" group -- this has the possibility of leaving a group bumbling about, but is otherwise non-serious.
- "username" groups -- this has security implications regarding PIs
- just force the admin to create a group
Change History (2)
comment:1 Changed 17 years ago by jmoore
comment:2 Changed 17 years ago by jmoore
- Resolution set to fixed
- Status changed from new to closed
Closing, since this is working for milestone:3.0-Beta1 . This may eventually be the solution we want to keep, but I'm leaving the "REVIEW" keyword.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
r1119 Adds a "default" group. This will be created after:
java omero quick clean install reload-db