Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 334139

Summary:	[client] An administrator view to manage users
Product:	[ECD] Orion	Reporter:	Szymon Brandys <Szymon.Brandys>
Component:	Client	Assignee:	Malgorzata Janczarska <malgorzata.tomczyk>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	bokowski, john.arthorne, simon_kaegi, tomasz.zarna
Version:	0.2
Target Milestone:	0.2
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:	335205
Bug Blocks:

Description Szymon Brandys

2011-01-12 12:14:08 EST

An administrator view to manage users/workspaces is needed

Comment 1 Szymon Brandys

2011-01-24 07:00:49 EST

We need a simple view for managing users. Gosia, please prepare the UI and I will handle the server side. 

The UI should let Administrators:
- create a new user 
- see all existing users and see their details
- change user authentication details such as passwords and roles
- delete users

Comment 2 Szymon Brandys

2011-01-24 10:41:54 EST

*** Bug 334363 has been marked as a duplicate of this bug. ***

Comment 3 Malgorzata Janczarska

2011-01-25 09:57:07 EST

If you import org.eclipse.orion.client.users.ui project from client repository and go the /manage-users.html site you will see the first version of the view. Look and feel and error handling needs to be improved, but all the basic operations can be done.
Of course your user needs to have certain rights to perform operations: /users (view users list) and /users/* (perform operations on users).

Comment 4 John Arthorne

2011-01-25 14:44:46 EST

Let's keep the client code together in org.eclipse.orion.client.core until we decide exactly how to divide it up. It seems arbitrary that this stuff is in a new bundle but for example auth.js and users.js are in the client core bundle. It can go in a separate directory to keep things organized.

Unlike with Java code, there isn't a significant advantage to creating new client bundles because it won't enforce any kind of separation at runtime.

Comment 5 John Arthorne

2011-01-25 14:45:39 EST

Simon/Boris, any thoughts on dividing the client into multiple bundles?

Comment 6 Szymon Brandys

2011-01-26 05:17:22 EST

This split was done on purpose. I see at least two reasons to keep admin UI in a separate bundle.
1) If one uses XML User Admin or custom non-editable User Admin, he would not like to see the admin UI. To achieve it, he could just remove the bundle.
2) Having user admin UI in a separate bundle let early adopters to replace this UI with custom one easily.

Comment 7 Malgorzata Janczarska

2011-01-26 07:21:23 EST

This bundle has dependency on client.core, so it can use all features implemented in it, so this is not a problem that some required files are placed in client.core.
As Szymon wrote a big advantage of having it in a separate bundle is that it can be removed or replaced. Remember that we allow our users to support only OpenId or any other custom authentication that is not compatible with this administrator view.

Comment 8 Szymon Brandys

2011-03-08 05:19:18 EST

Some improvements were done during M7. Marking fixed.

Comment 9 Szymon Brandys

2011-03-08 05:19:53 EST

(In reply to comment #8)
> Some improvements were done during M7.
... M6.