Hi Jason,
it looks like you could use contributor_profile content type for it.
More info: https://github.com/searchisko/searchisko/issues/24 resp. https://github.com/searchisko/searchisko/blob/master/documentation/rest-api/content/contributor_profile.md

ATM this profile is created when you “log in” to Searchisko via http://dcp-jbossorgdev.rhcloud.com/v1/rest/auth/status
Once task indexer will be in place (https://github.com/searchisko/searchisko/issues/31) then you’ll get all contributor profiles for all contributors.

Search query example: 
http://dcp-jbossorgdev.rhcloud.com/v1/rest/search?sys_type=contributor_profile&field=_source


WDYT?

Libor

Libor Krzyžanek
jboss.org Development Team

On 13 Feb 2014, at 18:10, Jason Porter <jporter@redhat.com> wrote:

What I'm looking to do right now is simply access the GET /rest/v1/contributor endpoint during site gen to pull the list of contributors we know about. I could do the search (still requiring the superuser) one at a time, but I'd really prefer to do a bulk request once than many small requests. Ideally we'd be able to add information about the user which may not be in the DCP (twitter handle, gravatar, etc.), but that isn't a must have that right now.

Honestly the authorization scheme currently in place in searchisko is a bit sub par (all or nothing). I've noticed we're using CAS and some role based checking scheme, further fleshing this out to be a bit more fine grained (at least read permissions for other trusted users) would be very helpful.

----- Original Message -----
From: "Lukas Vlcek" <lvlcek@redhat.com>
To: "Jason Porter" <jporter@redhat.com>
Cc: searchisko-dev@lists.jboss.org, "Libor Krzyžanek" <lkrzyzan@redhat.com>, "Vlastimil Elias" <velias@redhat.com>
Sent: Thursday, February 13, 2014 8:12:16 AM
Subject: Re: [searchisko-dev] adding a superuser?

Hi Jason,

if I understand correctly you want to use
http://docs.jbossorg.apiary.io/#managementapicontributors API but you would
prefer using different account than the superuser (jbossorg by default),
right? Do you think you can give me some example of use cases that you need
to handle? Internal management of contributors is quite delicate process (in
terms of how it is related to other systems) so we need to be sure that we
would not break anything by opening it for other [non-]superusers.

BTW both Libor and Vlastimil are more knowledgable about internals of process
behind contributors management.

You are correct that currently only one superuser account is allowed.

Regards,
Lukas Vlcek
jboss.org Development Team

----- Original Message -----
Its looking more and more like I'll need to be able to access the
contributor
service from the JBoss Developer build. I'd prefer to only use one user if
possible to handle all communication with the DCP/Searchisko. Currently I
believe only the jbossorg user is the only superuser. How do we go about
adding another one? I did some searching in the code base and configuration
files but didn't see anything, maybe I missed it. Any thoughts?
_______________________________________________
searchisko-dev mailing list
searchisko-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/searchisko-dev