1:02 p.m.
Greetings JBosstools Devs,
as discussed last week, we AERI now supports GitHub authentication and authorization in
addition to the previous username-password based authentication. That means you can now
log in with your GitHub account. Your roles (reviewer, admin, or just reporter) are
determined by your membership in the JBoss Tools GitHub organisation and teams. If you log
in and are forwarded to a /reporter/ URL, please contact your GitHub org admins (e.g.
Alexey or Fred) and ask them to review your team memberships.
Please note that you can still log in with the previous credentials. But this account may
be shut down by your org admins soon. Thus, please switch over to GitHub authorization
soon. Thank you.
If you experience insane login delays (say, 10 seconds and more) please let me know. There
might be a few things to tweak.
Have a great week,
Marcel
--
Codetrails GmbH
The knowledge transfer company
Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-179-131-7721
http://www.codetrails.com/
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
10:53 a.m.
Excellent work Marcel!
/max
Greetings JBosstools Devs,
as discussed last week, we AERI now supports GitHub authentication and
authorization in addition to the previous username-password based
authentication. That means you can now log in with your GitHub
account. Your roles (reviewer, admin, or just reporter) are determined
by your membership in the JBoss Tools GitHub organisation and teams.
If you log in and are forwarded to a /reporter/ URL, please contact
your GitHub org admins (e.g. Alexey or Fred) and ask them to review
your team memberships.
Please note that you can still log in with the previous credentials.
But this account may be shut down by your org admins soon. Thus,
please switch over to GitHub authorization soon. Thank you.
If you experience insane login delays (say, 10 seconds and more)
please let me know. There might be a few things to tweak.
Have a great week,
Marcel
--
Codetrails GmbH
The knowledge transfer company
Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-179-131-7721
http://www.codetrails.com/
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
/max
http://about.me/maxandersen
1:32 p.m.
Hi,
Today I wanted to check the problem that was behind this JIRA:
https://issues.jboss.org/browse/JBIDE-22655
<https://issues.jboss.org/browse/JBIDE-22655>
So I clicked the link to
https://redhat.ctrlflow.com/reviewers/#!/problems/571f44b6e4b0a5498327874b
<https://redhat.ctrlflow.com/reviewers/#!/problems/571f44b6e4b0a5498327874...
The page asked me to log in, so I logged in via github - I gave it permission to use my
github account.
Then I tried again and I get:
You do not have access to this view: /problems/571f44b6e4b0a5498327874b
What do I need to see this? I am a member of the JBoss Tools github organization. I think
this should be enough. Further, I am in the teams of devdoc and website.
BTW, https://redhat.ctrlflow.com/ <https://redhat.ctrlflow.com/> gives this:
{"timestamp":1469705301444,"status":404,"error":"Not
Found","message":"No message
available","path":"/"}
And https://redhat.ctrlflow.com/reviewers/#!/
<https://redhat.ctrlflow.com/reviewers/#!/> gives this:
You do not have access to this view: /
Thanks,
Martin
--
Martin Malina
JBoss QA Engineer
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno, Czech Republic
Tel.: +420 532 294 265
On 25. 7. 2016, at 13:02, Marcel Bruch
<marcel.bruch(a)codetrails.com> wrote:
Greetings JBosstools Devs,
as discussed last week, we AERI now supports GitHub authentication and authorization in
addition to the previous username-password based authentication. That means you can now
log in with your GitHub account. Your roles (reviewer, admin, or just reporter) are
determined by your membership in the JBoss Tools GitHub organisation and teams. If you log
in and are forwarded to a /reporter/ URL, please contact your GitHub org admins (e.g.
Alexey or Fred) and ask them to review your team memberships.
Please note that you can still log in with the previous credentials. But this account may
be shut down by your org admins soon. Thus, please switch over to GitHub authorization
soon. Thank you.
If you experience insane login delays (say, 10 seconds and more) please let me know.
There might be a few things to tweak.
Have a great week,
Marcel
--
Codetrails GmbH
The knowledge transfer company
Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-179-131-7721
http://www.codetrails.com/ <http://www.codetrails.com/>
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
2:16 p.m.
Martin,
I just checked your roles. You only got Reporter rights assigned (the default) b/c your
teams devdoc and website were not enabled for reviewer access by your org-admins.
Org-admins, is this an oversight?
BTW, https://redhat.ctrlflow.com/
<https://redhat.ctrlflow.com/> gives this:
{"timestamp":1469705301444,"status":404,"error":"Not
Found","message":"No message
available","path":"/"}
Agreed, we should make this more meaningful again.
Marcel
2:34 p.m.
On 28 Jul 2016, at 14:16, Marcel Bruch wrote:
Martin,
I just checked your roles. You only got Reporter rights assigned (the
default) b/c your teams devdoc and website were not enabled for
reviewer access by your org-admins.
what does reviewer access mean in this context ?
Would it be sufficient to add a read-only group that have access to all
repos and add everyone without push access to look ?
/max
Org-admins, is this an oversight?
> BTW, https://redhat.ctrlflow.com/ <https://redhat.ctrlflow.com/>
> gives this:
>
{"timestamp":1469705301444,"status":404,"error":"Not
> Found","message":"No message
available","path":"/"}
Agreed, we should make this more meaningful again.
Marcel
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
/max
http://about.me/maxandersen
2:52 p.m.
Max,
On 28 Jul 2016, at 14:34, Max Rydahl Andersen
<manderse(a)redhat.com> wrote:
On 28 Jul 2016, at 14:16, Marcel Bruch wrote:
> Martin,
>
> I just checked your roles. You only got Reporter rights assigned (the default) b/c
your teams devdoc and website were not enabled for reviewer access by your org-admins.
what does reviewer access mean in this context ?
There are three roles: reporters, reviewers and org-admins. Reporters can only see public
information of a problem while reviewers can edit data, create bugs etc. org-admins can
administrate different aspects of the installation.
Would it be sufficient to add a read-only group that have access to
all repos and add everyone without push access to look ?
I’ve discussed several options with Fred and Alexey last week.
Just repeating them briefly:
1. If all organization members should get reviewer access, simply do no select any team.
We’ll then check membership against the organization members.
2. It may make sense to create a group especially for accessing error reports (e.g. aeri).
There simply add everyone who needs access to error reports.
3. If some teams should not / do not require access to error reports, simply do not select
their teams in the oauth authorization panel - that’s what’s used ATM.
Whatever you decide, just update the configuration - or let me know.
Please note that you still can log in with the previously used username/password.
Marcel
/max
>
> Org-admins, is this an oversight?
>
>> BTW, https://redhat.ctrlflow.com/ <https://redhat.ctrlflow.com/> gives
this:
>>
{"timestamp":1469705301444,"status":404,"error":"Not
Found","message":"No message
available","path":"/"}
>
> Agreed, we should make this more meaningful again.
>
> Marcel
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
/max
http://about.me/maxandersen
--
Codetrails GmbH
The knowledge transfer company
Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-179-131-7721
http://www.codetrails.com/
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
3 p.m.
Hi Marcel,
Thanks for the details. I don't think the solution is to add devdoc and website teams
- there are still many in our QE team who are in neither of these. In my opinion, it would
make sense to just give the reporter role to the whole jbosstools team on github. But as
you say, this has to be decided by the org-admins - Alexey and Fred?
-Martin
On 28. 7. 2016, at 14:52, Marcel Bruch
<marcel.bruch(a)codetrails.com> wrote:
Max,
> On 28 Jul 2016, at 14:34, Max Rydahl Andersen <manderse(a)redhat.com
<mailto:manderse@redhat.com>> wrote:
>
> On 28 Jul 2016, at 14:16, Marcel Bruch wrote:
>
>> Martin,
>>
>> I just checked your roles. You only got Reporter rights assigned (the default)
b/c your teams devdoc and website were not enabled for reviewer access by your
org-admins.
>
> what does reviewer access mean in this context ?
There are three roles: reporters, reviewers and org-admins. Reporters can only see public
information of a problem while reviewers can edit data, create bugs etc. org-admins can
administrate different aspects of the installation.
> Would it be sufficient to add a read-only group that have access to all repos and add
everyone without push access to look ?
I’ve discussed several options with Fred and Alexey last week.
Just repeating them briefly:
1. If all organization members should get reviewer access, simply do no select any team.
We’ll then check membership against the organization members.
2. It may make sense to create a group especially for accessing error reports (e.g.
aeri). There simply add everyone who needs access to error reports.
3. If some teams should not / do not require access to error reports, simply do not
select their teams in the oauth authorization panel - that’s what’s used ATM.
Whatever you decide, just update the configuration - or let me know.
Please note that you still can log in with the previously used username/password.
Marcel
>
> /max
>>
>> Org-admins, is this an oversight?
>>
>>> BTW, https://redhat.ctrlflow.com/ <https://redhat.ctrlflow.com/>
<https://redhat.ctrlflow.com/ <https://redhat.ctrlflow.com/>> gives this:
>>>
{"timestamp":1469705301444,"status":404,"error":"Not
Found","message":"No message
available","path":"/"}
>>
>> Agreed, we should make this more meaningful again.
>>
>> Marcel
>
>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev(a)lists.jboss.org <mailto:jbosstools-dev@lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> /max
> http://about.me/maxandersen <http://about.me/maxandersen>
--
Codetrails GmbH
The knowledge transfer company
Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-179-131-7721
http://www.codetrails.com/ <http://www.codetrails.com/>
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
3:32 p.m.
On 28 Jul 2016, at 15:00, Martin Malina <mmalina(a)redhat.com>
wrote:
In my opinion, it would make sense to just give the reporter role to the whole jbosstools
team on github.
Just a minor correction:
We use different URL prefixes for reviewers and reporters. If a “reporter" accesses a
“reviewer" url, he/she gets an "access denied”. That’s what you got when
clicking on a JIRA link.
The different url prefixes were required in previous versions of AERI. We could, however,
change the current system to use only one url and so that *all* reporters get a
public/anonymized view of a problem. Please note the word anonymized. Problems may contain
senstive information like email addresses, error messages etc. We thus cannot make them
public available to everyone as-is.
However, at Eclipse we agreed on showing a anonymized view might be perfectly okay. So we
could do the same here.
Max, Alexey, Fred,
what do you think?
2:30 a.m.
I think we should grant reviewer access to all members of jbosstools org. For example QE
may not have push access in github but we still want them be able to create issues based
on aeri reports.
Regarding links in jira... Ideally the same link should work for everyone with optional
GitHub authentication. If you do not login or you are not a jbosstools org member you see
a public version of the report. Otherwise you see what you are supposed to see
corresponding to your role.
If it requires significant efforts to implement then can we post a few links for different
roles with clear descriptions as a workaround?
WDYT?
On Jul 28, 2016, at 6:32 AM, Marcel Bruch
<marcel.bruch(a)codetrails.com> wrote:
> On 28 Jul 2016, at 15:00, Martin Malina <mmalina(a)redhat.com> wrote:
> In my opinion, it would make sense to just give the reporter role to the whole
jbosstools team on github.
Just a minor correction:
We use different URL prefixes for reviewers and reporters. If a “reporter" accesses
a “reviewer" url, he/she gets an "access denied”. That’s what you got when
clicking on a JIRA link.
The different url prefixes were required in previous versions of AERI. We could, however,
change the current system to use only one url and so that *all* reporters get a
public/anonymized view of a problem. Please note the word anonymized. Problems may contain
senstive information like email addresses, error messages etc. We thus cannot make them
public available to everyone as-is.
However, at Eclipse we agreed on showing a anonymized view might be perfectly okay. So we
could do the same here.
Max, Alexey, Fred,
what do you think?
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
2:06 p.m.
On 30. 7. 2016, at 2:30, Alexey Kazakov <alkazako(a)redhat.com>
wrote:
I think we should grant reviewer access to all members of jbosstools org. For example QE
may not have push access in github but we still want them be able to create issues based
on aeri reports.
I agree :) So can you make it happen please, Marcel?
Thanks,
Martin
Regarding links in jira... Ideally the same link should work for
everyone with optional GitHub authentication. If you do not login or you are not a
jbosstools org member you see a public version of the report. Otherwise you see what you
are supposed to see corresponding to your role.
If it requires significant efforts to implement then can we post a few links for
different roles with clear descriptions as a workaround?
WDYT?
On Jul 28, 2016, at 6:32 AM, Marcel Bruch <marcel.bruch(a)codetrails.com
<mailto:marcel.bruch@codetrails.com>> wrote:
>
>> On 28 Jul 2016, at 15:00, Martin Malina <mmalina(a)redhat.com
<mailto:mmalina@redhat.com>> wrote:
>> In my opinion, it would make sense to just give the reporter role to the whole
jbosstools team on github.
>
> Just a minor correction:
>
> We use different URL prefixes for reviewers and reporters. If a “reporter"
accesses a “reviewer" url, he/she gets an "access denied”. That’s what you got
when clicking on a JIRA link.
>
> The different url prefixes were required in previous versions of AERI. We could,
however, change the current system to use only one url and so that *all* reporters get a
public/anonymized view of a problem. Please note the word anonymized. Problems may contain
senstive information like email addresses, error messages etc. We thus cannot make them
public available to everyone as-is.
>
> However, at Eclipse we agreed on showing a anonymized view might be perfectly okay.
So we could do the same here.
>
> Max, Alexey, Fred,
> what do you think?
>
>
>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org <mailto:jbosstools-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
<https://lists.jboss.org/mailman/listinfo/jbosstools-dev>
3:28 p.m.
On 2 Aug 2016, at 14:06, Martin Malina wrote:
> On 30. 7. 2016, at 2:30, Alexey Kazakov
<alkazako(a)redhat.com> wrote:
>
> I think we should grant reviewer access to all members of jbosstools
> org. For example QE may not have push access in github but we still
> want them be able to create issues based on aeri reports.
I agree :) So can you make it happen please, Marcel?
+1
As long as the possible private sensitive data are not publically
available
and we know who have access and we can add/remove people we should be
fine.
And by we I mean JBoss Tools and Developer Studio development team.
/max
Thanks,
Martin
> Regarding links in jira... Ideally the same link should work for
> everyone with optional GitHub authentication. If you do not login or
> you are not a jbosstools org member you see a public version of the
> report. Otherwise you see what you are supposed to see corresponding
> to your role.
> If it requires significant efforts to implement then can we post a
> few links for different roles with clear descriptions as a
> workaround?
>
> WDYT?
>
>
> On Jul 28, 2016, at 6:32 AM, Marcel Bruch
> <marcel.bruch(a)codetrails.com <mailto:marcel.bruch@codetrails.com>>
> wrote:
>
>>
>>> On 28 Jul 2016, at 15:00, Martin Malina <mmalina(a)redhat.com
>>> <mailto:mmalina@redhat.com>> wrote:
>>> In my opinion, it would make sense to just give the reporter role
>>> to the whole jbosstools team on github.
>>
>> Just a minor correction:
>>
>> We use different URL prefixes for reviewers and reporters. If a
>> “reporter" accesses a “reviewer" url, he/she gets an "access
>> denied”. That’s what you got when clicking on a JIRA link.
>>
>> The different url prefixes were required in previous versions of
>> AERI. We could, however, change the current system to use only one
>> url and so that *all* reporters get a public/anonymized view of a
>> problem. Please note the word anonymized. Problems may contain
>> senstive information like email addresses, error messages etc. We
>> thus cannot make them public available to everyone as-is.
>>
>> However, at Eclipse we agreed on showing a anonymized view might be
>> perfectly okay. So we could do the same here.
>>
>> Max, Alexey, Fred,
>> what do you think?
>>
>>
>>
>>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev(a)lists.jboss.org
>> <mailto:jbosstools-dev@lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>> <https://lists.jboss.org/mailman/listinfo/jbosstools-dev>
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
/max
http://about.me/maxandersen
9:38 a.m.
On 02 Aug 2016, at 15:28, Max Rydahl Andersen
<manderse(a)redhat.com> wrote:
On 2 Aug 2016, at 14:06, Martin Malina wrote:
>> On 30. 7. 2016, at 2:30, Alexey Kazakov <alkazako(a)redhat.com> wrote:
>>
>> I think we should grant reviewer access to all members of jbosstools
>> org.
> I agree :) So can you make it happen please, Marcel?
+1
I cleared the teams. Now authorization is checked against organization membership only,
not team membership. QE should have full access after logging in with GitHub (w/o log in
you still get access denied).
Marcel
11:23 a.m.
On 3. 8. 2016, at 9:38, Marcel Bruch
<marcel.bruch(a)codetrails.com> wrote:
> On 02 Aug 2016, at 15:28, Max Rydahl Andersen <manderse(a)redhat.com
<mailto:manderse@redhat.com>> wrote:
>
> On 2 Aug 2016, at 14:06, Martin Malina wrote:
>
>>> On 30. 7. 2016, at 2:30, Alexey Kazakov <alkazako(a)redhat.com
<mailto:alkazako@redhat.com>> wrote:
>>>
>>> I think we should grant reviewer access to all members of jbosstools
>>> org.
>> I agree :) So can you make it happen please, Marcel?
>
> +1
I cleared the teams. Now authorization is checked against organization membership only,
not team membership. QE should have full access after logging in with GitHub (w/o log in
you still get access denied).
It still doesn't work for me. I still get access denied for pages like [1]. BTW, I
suggest you put some valid content at https://redhat.ctrlflow.com
<https://redhat.ctrlflow.com/> . Because right now I'm logged in with a user
that can't access /reviewers/, there is nothing at / and I would be screwed if I
didn't know about /reporters/ - so I went there, logged out and tried logging in again
with github, but that didn't help. My username is mmalina .
-Martin
[1] https://redhat.ctrlflow.com/reviewers/#!/problems/571f44b6e4b0a5498327874b
<https://redhat.ctrlflow.com/reviewers/#!/problems/571f44b6e4b0a5498327874... ,
https://redhat.ctrlflow.com/reviewers#!/
Marcel
1:06 p.m.
On 03 Aug 2016, at 11:23, Martin Malina <mmalina(a)redhat.com>
wrote:
>
> On 3. 8. 2016, at 9:38, Marcel Bruch <marcel.bruch(a)codetrails.com
<mailto:marcel.bruch@codetrails.com>> wrote:
>
>
>> On 02 Aug 2016, at 15:28, Max Rydahl Andersen <manderse(a)redhat.com
<mailto:manderse@redhat.com>> wrote:
>>
>> On 2 Aug 2016, at 14:06, Martin Malina wrote:
>>
>>>> On 30. 7. 2016, at 2:30, Alexey Kazakov <alkazako(a)redhat.com
<mailto:alkazako@redhat.com>> wrote:
>>>>
>>>> I think we should grant reviewer access to all members of jbosstools
>>>> org.
>>> I agree :) So can you make it happen please, Marcel?
>>
>> +1
>
> I cleared the teams. Now authorization is checked against organization membership
only, not team membership. QE should have full access after logging in with GitHub (w/o
log in you still get access denied).
It still doesn't work for me.
My excuse. It’s an oversight on my end.
The system placed you in the “local database” authorization group after your first login
b/c the JBoss Teams did not return any match for your username. I set all *(a)redhat.com
<http://redhat.com/> users back to GitHub authorization. You should be able to log
in as reviewer now.
Marcel
2:47 p.m.
On 3. 8. 2016, at 13:06, Marcel Bruch
<marcel.bruch(a)codetrails.com> wrote:
>
> On 03 Aug 2016, at 11:23, Martin Malina <mmalina(a)redhat.com
<mailto:mmalina@redhat.com>> wrote:
>
>>
>> On 3. 8. 2016, at 9:38, Marcel Bruch <marcel.bruch(a)codetrails.com
<mailto:marcel.bruch@codetrails.com>> wrote:
>>
>>
>>> On 02 Aug 2016, at 15:28, Max Rydahl Andersen <manderse(a)redhat.com
<mailto:manderse@redhat.com>> wrote:
>>>
>>> On 2 Aug 2016, at 14:06, Martin Malina wrote:
>>>
>>>>> On 30. 7. 2016, at 2:30, Alexey Kazakov <alkazako(a)redhat.com
<mailto:alkazako@redhat.com>> wrote:
>>>>>
>>>>> I think we should grant reviewer access to all members of jbosstools
>>>>> org.
>>>> I agree :) So can you make it happen please, Marcel?
>>>
>>> +1
>>
>> I cleared the teams. Now authorization is checked against organization membership
only, not team membership. QE should have full access after logging in with GitHub (w/o
log in you still get access denied).
>
> It still doesn't work for me.
My excuse. It’s an oversight on my end.
The system placed you in the “local database” authorization group after your first login
b/c the JBoss Teams did not return any match for your username. I set all *(a)redhat.com
<http://redhat.com/> users back to GitHub authorization. You should be able to log
in as reviewer now.
Yes, it works now! Thanks!
-Martin
Marcel
2823
days inactive
2832
days old
jbosstools-dev@lists.jboss.org
14 comments
4 participants
participants (4)
-
Alexey Kazakov -
Marcel Bruch -
Martin Malina -
Max Rydahl Andersen