Hi Viknes, Further consider adding other user related operations into admin UI you are developing. Other operations include; 1. Adding system users 2. Deleting system users 3. Changing password
All these operations are currently implemented in org.apache.airavata.services.registry.rest.security.local.LocalUserStore [1]. You may expose these functionalities through the API. [1] https://svn.apache.org/repos/asf/airavata/trunk/modules/rest/service/src/main/java/org/apache/airavata/services/registry/rest/security/local/LocalUserStore.java Thanks Amila On Mon, Jul 8, 2013 at 4:09 PM, Viknes Balasubramanee <[email protected]>wrote: > I have created a JIRA for this and have created a simple registry to get me > the list of users in the registry. Please verify the structure of this so > that > I can proceed further with implementing other required methods. Also if you > have any methods that you feel should be added, please comment about them > in > the JIRA issue. > > https://issues.apache.org/jira/browse/AIRAVATA-880 > > Thanks > Viknes > > -----Original Message----- > From: Saminda Wijeratne [mailto:[email protected]] > Sent: Tuesday, July 02, 2013 12:16 AM > To: [email protected] > Cc: viknesb > Subject: Re: API to get list of users > > On Mon, Jul 1, 2013 at 10:34 PM, Suresh Marru <[email protected]> wrote: > > > On Jul 1, 2013, at 10:27 PM, Amila Jayasekara > > <[email protected]> > > wrote: > > > > > Hi Viknes, > > > > > > I am sorry, I was under the impression you are using AiravataAPI. > > > But > > seems > > > you are using the registry api. Therefore +1 for creating > > > UserRegistry > > and > > > adding user related methods. > > > > + 1. Technically Viknes's gsoc project has two parts. His > > + contributions of > > a administrative monitoring dashboard can become a component within > > Airavata. For this t is justified to use the more internal Registry > > API with less stringent security requirements (assuming the web app > > can be co-hosted with the server). But if we look at the other side of > > this gsoc project, the goal was to make this administrative web > > interface "embeddable" into downstream portals. These interfaces > > should ideally use Airavata API and follow standard integration > > security requirements. But for now, we probably can focus on the > > internal (bundled administrative interface). > > > +1 > > > > > Suresh > > > > > > > > Thanks > > > Amila > > > > > > > > > On Mon, Jul 1, 2013 at 8:35 PM, Amila Jayasekara < > > [email protected]>wrote: > > > > > >> Hi Viknes, > > >> > > >> Please see some comments inline. > > >> > > >> > > >> On Mon, Jul 1, 2013 at 4:19 PM, Viknes Balasubramanee > > >> <[email protected] > > >wrote: > > >> > > >>> To add these new methods, I would like to create a new API in the > > registry > > >>> called as UserRegistry and have all user related operations > > >>> available through it. > > >>> > > >> > > >> There is already an interface > > >> called org.apache.airavata.client.api.UserManager. > > >> Please add your methods to that. > > >> > > >> > > >>> > > >>> Opinions pls? > > >>> > > >>> Also after a user has authenticated himself using basic > > authentication, I > > >>> see a cookie is set and it can be used for further requests. Is > > >>> there a logout method that would clear a user's session and the > > >>> cookie? If > > not, I > > >>> would like to add it to the new API as well. > > >>> > > >> > > >> There isnt a logout method. Please go a head and implement it. > > > I suggest to use the java interface > org.apache.airavata.registry.api.AiravataSubRegistry to include the > functions > like, > connect() > disconnect() > "logout" sounds more impl specific. Also your patch will have to update the > isActive() function which is already there to support the changes you are > making. > > Saminda > > >> > > >> Thanks > > >> Amila > > >> > > >> > > >>> > > >>> Thanks > > >>> Viknes > > >>> > > >>> -----Original Message----- > > >>> From: Saminda Wijeratne [mailto:[email protected]] > > >>> Sent: Friday, June 28, 2013 4:05 PM > > >>> To: [email protected]; [email protected] > > >>> Subject: Re: API to get list of users > > >>> > > >>> +1 > > >>> > > >>> > > >>> On Fri, Jun 28, 2013 at 11:25 AM, Viknes Balasubramanee > > >>> <[email protected]>wrote: > > >>> > > >>>> I don't have a list right now. I can take this up on me, work on > > >>>> it and submit a patch if that's ok. > > >>>> > > >>>> Thanks > > >>>> Viknes > > >>>> > > >>>> -----Original Message----- > > >>>> From: Saminda Wijeratne [mailto:[email protected]] > > >>>> Sent: Friday, June 28, 2013 9:15 AM > > >>>> To: [email protected]; [email protected] > > >>>> Subject: Re: API to get list of users > > >>>> > > >>>> We don't. User management functions are never focused upon in the > > >>>> API so far. Can you sort of list the functions you need for users > > >>>> in the API? We can workout to add them in the 0.9 release API. > > >>>> > > >>>> > > >>>> On Thu, Jun 27, 2013 at 4:28 PM, Viknes Balasubramanee > > >>>> <[email protected]>wrote: > > >>>> > > >>>>> Hi,**** > > >>>>> > > >>>>> ** ** > > >>>>> > > >>>>> I was wondering if there is an API (REST) to get a list of all > > >>>>> users in the database. This is required for the admin monitoring > > >>>>> dashboard that I am developing and I want an admin user to be > > >>>>> able to look at the list of users in the system.**** > > >>>>> > > >>>>> ** ** > > >>>>> > > >>>>> Thanks**** > > >>>>> > > >>>>> Viknes**** > > >>>>> > > >>>> > > >>> > > >> > > >> > > > > >
