You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by Michael Matthews <ma...@oclc.org> on 2012/01/13 19:59:59 UTC
Allowing an authorization server to provide an updated scope for
OAuth2 tokens
Section 3.3 [1] of the OAuth2 spec suggests that an authorization server may
issue an access token with a scope different than what was requested. It
goes on to say that the authorization server SHOULD include a "scope"
response parameter to inform the client of the actual scope granted.
We'd like to take advantage of this in our internally developed
authorization server. However it appears that Shindig does not look for this
"scope" parameter in the access token response. It always uses the scope
specified in the gadget (which is stored in the OAuth2Accessor).
It seems to me that the TokenAuthorizationResponseHandler should check the
response from the token endpoint to see if it contains an updated scope
instead of only using the scope from the OAuth2Accessor. Does this seem
like a reasonable interpretation of the OAuth2 spec? If so, I'd be happy to
create a JIRA and contribute a patch.
Thanks
Mike
[1] http://tools.ietf.org/html/draft-ietf-oauth-v2-21#section-3.3
Re: Shindig 3.0 timeline
Posted by Ryan J Baxter <rj...@us.ibm.com>.
Me too. I think Paul just needs to give us more privileges.
Regards,
RYAN J. BAXTER
Software Engineer - OpenSocial
IBM Collaboration Solutions
Phone: 1-978-899-3041
E-mail: rjbaxter@us.ibm.com
Blog: ryanjbaxter.com
Chat: rbaxter85 ryanjasonbaxter
Find me on: and within IBM on:
550 King St
Littleton, MA 01460-1250
United States
From: Dan Dumont/Westford/IBM@Lotus
To: dev@shindig.apache.org,
Cc: aed13@cornell.edu
Date: 01/25/2012 11:30 AM
Subject: Re: Shindig 3.0 timeline
Paul,
I'd like to address some of the JIRAs (close or reassign), but it appears
that I cannot modify or close JIRAs that I have not created.
Is there a way for me to get this power? Or do I need to hunt down the
people who created them and ask them to assign them or close them?
From: Paul Lindner <li...@inuus.com>
To: dev@shindig.apache.org, aed13@cornell.edu,
Date: 01/25/2012 03:57 AM
Subject: Re: Shindig 3.0 timeline
Hi Folks.
I started a little housekeeping for 3.0.0:
http://goo.gl/cBNk0
Please add or modify bugs so we only have release blockers that have a
definitive fix. Feel free to bump to 3.1.0 which is the next version we
can work on.
If you need/want higher-level Jira access let me know.
On Fri, Jan 20, 2012 at 9:05 AM, Andrew Davis
<an...@gmail.com>wrote:
> Paul,
>
> Our team is reviewing the list of open JIRAs as requested, and I think
we
> will have a response back to you on Monday or tuesday.
>
> I think it would be much more predictable for the community and
dependent
> products, if we published a schedule for locking down 3.0, with some one
> or two release candidates planned over a few weeks, as I suspect many
> team's like ours have been in active development and need some time to
> review test coverage before we declare a 3.0 GA.
>
> Aside from the 3.0 immediate release, it would also be helpful to
publish a
> regular release plan, maybe with a fixed annual schedule like Eclipse?
> Thoughts?
>
> --Andrew Davis
> IBM
>
> On Fri, Jan 20, 2012 at 9:55 AM, Paul Lindner <li...@inuus.com> wrote:
>
> > I'm not keen on version numbers myself.
> >
> > We can release at any time really, code is stable, tests are all
green.
> >
> > If someone wants to sign up to do maint releases of 3.0.x that would
be
> > helpful.
> >
> > Vote:
> > Release current trunk as shindig-3.0.0, move trunk to 3.1.0-SNAPSHOT
> >
> > [ ] +1 do it
> > [ ] +0 meh
> > [ ] -1 I have just one more patch.
> >
> > If you do -1 please provide code-review links or jira issues you
consider
> > blockers for 3.0.0
> >
> > On Fri, Jan 20, 2012 at 3:51 AM, Derek Houghton <de...@chuwori.co.uk>
> > wrote:
> >
> > > Hi,
> > > Didn't catch a reply to this?
> > > Could you tell me when stable shindig 3.0 is due for public release?
> > >
> > > Thanks
> > > Derek
> > >
> > >
> > > On 16 Jan 2012, at 10:57, Evgeny Bogdanov wrote:
> > >
> > > > Hello,
> > > >
> > > > when the shindig 3.0 is due?
> > > >
> > > > Best
> > > > Evgeny
> > >
> > >
> >
> >
> > --
> > Paul Lindner -- lindner@inuus.com -- profiles.google.com/pmlindner
> >
>
--
Paul Lindner -- lindner@inuus.com -- profiles.google.com/pmlindner
Re: Shindig 3.0 timeline
Posted by Dan Dumont <dd...@us.ibm.com>.
Works great for me now. Thanks!
From: Paul Lindner <li...@inuus.com>
To: dev@shindig.apache.org,
Cc: aed13@cornell.edu
Date: 01/25/2012 11:48 AM
Subject: Re: Shindig 3.0 timeline
I added (I think!) all the committers we voted in recently. Reload jira
and give it a go.
Also, if you want to have full admin rights on jira I'm happy to grant
that
too.
On Wed, Jan 25, 2012 at 8:28 AM, Dan Dumont <dd...@us.ibm.com> wrote:
> Paul,
>
> I'd like to address some of the JIRAs (close or reassign), but it
appears
> that I cannot modify or close JIRAs that I have not created.
> Is there a way for me to get this power? Or do I need to hunt down the
> people who created them and ask them to assign them or close them?
>
>
>
> From: Paul Lindner <li...@inuus.com>
> To: dev@shindig.apache.org, aed13@cornell.edu,
> Date: 01/25/2012 03:57 AM
> Subject: Re: Shindig 3.0 timeline
>
>
>
> Hi Folks.
>
> I started a little housekeeping for 3.0.0:
>
> http://goo.gl/cBNk0
>
> Please add or modify bugs so we only have release blockers that have a
> definitive fix. Feel free to bump to 3.1.0 which is the next version we
> can work on.
>
>
> If you need/want higher-level Jira access let me know.
>
>
> On Fri, Jan 20, 2012 at 9:05 AM, Andrew Davis
> <an...@gmail.com>wrote:
>
> > Paul,
> >
> > Our team is reviewing the list of open JIRAs as requested, and I think
> we
> > will have a response back to you on Monday or tuesday.
> >
> > I think it would be much more predictable for the community and
> dependent
> > products, if we published a schedule for locking down 3.0, with some
one
> > or two release candidates planned over a few weeks, as I suspect many
> > team's like ours have been in active development and need some time to
> > review test coverage before we declare a 3.0 GA.
> >
> > Aside from the 3.0 immediate release, it would also be helpful to
> publish a
> > regular release plan, maybe with a fixed annual schedule like Eclipse?
> > Thoughts?
> >
> > --Andrew Davis
> > IBM
> >
> > On Fri, Jan 20, 2012 at 9:55 AM, Paul Lindner <li...@inuus.com>
wrote:
> >
> > > I'm not keen on version numbers myself.
> > >
> > > We can release at any time really, code is stable, tests are all
> green.
> > >
> > > If someone wants to sign up to do maint releases of 3.0.x that would
> be
> > > helpful.
> > >
> > > Vote:
> > > Release current trunk as shindig-3.0.0, move trunk to
3.1.0-SNAPSHOT
> > >
> > > [ ] +1 do it
> > > [ ] +0 meh
> > > [ ] -1 I have just one more patch.
> > >
> > > If you do -1 please provide code-review links or jira issues you
> consider
> > > blockers for 3.0.0
> > >
> > > On Fri, Jan 20, 2012 at 3:51 AM, Derek Houghton
<de...@chuwori.co.uk>
> > > wrote:
> > >
> > > > Hi,
> > > > Didn't catch a reply to this?
> > > > Could you tell me when stable shindig 3.0 is due for public
release?
> > > >
> > > > Thanks
> > > > Derek
> > > >
> > > >
> > > > On 16 Jan 2012, at 10:57, Evgeny Bogdanov wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > when the shindig 3.0 is due?
> > > > >
> > > > > Best
> > > > > Evgeny
> > > >
> > > >
> > >
> > >
> > > --
> > > Paul Lindner -- lindner@inuus.com -- profiles.google.com/pmlindner
> > >
> >
>
>
>
> --
> Paul Lindner -- lindner@inuus.com -- profiles.google.com/pmlindner
>
>
--
Paul Lindner -- lindner@inuus.com -- profiles.google.com/pmlindner
Re: Shindig 3.0 timeline
Posted by Ryan J Baxter <rj...@us.ibm.com>.
Paul doesn't look like I have the right permissions to edit JIRAs I did
not create, can you double check for me?
Regards,
RYAN J. BAXTER
Software Engineer - OpenSocial
IBM Collaboration Solutions
Phone: 1-978-899-3041
E-mail: rjbaxter@us.ibm.com
Blog: ryanjbaxter.com
Chat: rbaxter85 ryanjasonbaxter
Find me on: and within IBM on:
550 King St
Littleton, MA 01460-1250
United States
From: Paul Lindner <li...@inuus.com>
To: dev@shindig.apache.org,
Cc: aed13@cornell.edu
Date: 01/25/2012 11:46 AM
Subject: Re: Shindig 3.0 timeline
I added (I think!) all the committers we voted in recently. Reload jira
and give it a go.
Also, if you want to have full admin rights on jira I'm happy to grant
that
too.
On Wed, Jan 25, 2012 at 8:28 AM, Dan Dumont <dd...@us.ibm.com> wrote:
> Paul,
>
> I'd like to address some of the JIRAs (close or reassign), but it
appears
> that I cannot modify or close JIRAs that I have not created.
> Is there a way for me to get this power? Or do I need to hunt down the
> people who created them and ask them to assign them or close them?
>
>
>
> From: Paul Lindner <li...@inuus.com>
> To: dev@shindig.apache.org, aed13@cornell.edu,
> Date: 01/25/2012 03:57 AM
> Subject: Re: Shindig 3.0 timeline
>
>
>
> Hi Folks.
>
> I started a little housekeeping for 3.0.0:
>
> http://goo.gl/cBNk0
>
> Please add or modify bugs so we only have release blockers that have a
> definitive fix. Feel free to bump to 3.1.0 which is the next version we
> can work on.
>
>
> If you need/want higher-level Jira access let me know.
>
>
> On Fri, Jan 20, 2012 at 9:05 AM, Andrew Davis
> <an...@gmail.com>wrote:
>
> > Paul,
> >
> > Our team is reviewing the list of open JIRAs as requested, and I think
> we
> > will have a response back to you on Monday or tuesday.
> >
> > I think it would be much more predictable for the community and
> dependent
> > products, if we published a schedule for locking down 3.0, with some
one
> > or two release candidates planned over a few weeks, as I suspect many
> > team's like ours have been in active development and need some time to
> > review test coverage before we declare a 3.0 GA.
> >
> > Aside from the 3.0 immediate release, it would also be helpful to
> publish a
> > regular release plan, maybe with a fixed annual schedule like Eclipse?
> > Thoughts?
> >
> > --Andrew Davis
> > IBM
> >
> > On Fri, Jan 20, 2012 at 9:55 AM, Paul Lindner <li...@inuus.com>
wrote:
> >
> > > I'm not keen on version numbers myself.
> > >
> > > We can release at any time really, code is stable, tests are all
> green.
> > >
> > > If someone wants to sign up to do maint releases of 3.0.x that would
> be
> > > helpful.
> > >
> > > Vote:
> > > Release current trunk as shindig-3.0.0, move trunk to
3.1.0-SNAPSHOT
> > >
> > > [ ] +1 do it
> > > [ ] +0 meh
> > > [ ] -1 I have just one more patch.
> > >
> > > If you do -1 please provide code-review links or jira issues you
> consider
> > > blockers for 3.0.0
> > >
> > > On Fri, Jan 20, 2012 at 3:51 AM, Derek Houghton
<de...@chuwori.co.uk>
> > > wrote:
> > >
> > > > Hi,
> > > > Didn't catch a reply to this?
> > > > Could you tell me when stable shindig 3.0 is due for public
release?
> > > >
> > > > Thanks
> > > > Derek
> > > >
> > > >
> > > > On 16 Jan 2012, at 10:57, Evgeny Bogdanov wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > when the shindig 3.0 is due?
> > > > >
> > > > > Best
> > > > > Evgeny
> > > >
> > > >
> > >
> > >
> > > --
> > > Paul Lindner -- lindner@inuus.com -- profiles.google.com/pmlindner
> > >
> >
>
>
>
> --
> Paul Lindner -- lindner@inuus.com -- profiles.google.com/pmlindner
>
>
--
Paul Lindner -- lindner@inuus.com -- profiles.google.com/pmlindner
Re: Shindig 3.0 timeline
Posted by Paul Lindner <li...@inuus.com>.
I added (I think!) all the committers we voted in recently. Reload jira
and give it a go.
Also, if you want to have full admin rights on jira I'm happy to grant that
too.
On Wed, Jan 25, 2012 at 8:28 AM, Dan Dumont <dd...@us.ibm.com> wrote:
> Paul,
>
> I'd like to address some of the JIRAs (close or reassign), but it appears
> that I cannot modify or close JIRAs that I have not created.
> Is there a way for me to get this power? Or do I need to hunt down the
> people who created them and ask them to assign them or close them?
>
>
>
> From: Paul Lindner <li...@inuus.com>
> To: dev@shindig.apache.org, aed13@cornell.edu,
> Date: 01/25/2012 03:57 AM
> Subject: Re: Shindig 3.0 timeline
>
>
>
> Hi Folks.
>
> I started a little housekeeping for 3.0.0:
>
> http://goo.gl/cBNk0
>
> Please add or modify bugs so we only have release blockers that have a
> definitive fix. Feel free to bump to 3.1.0 which is the next version we
> can work on.
>
>
> If you need/want higher-level Jira access let me know.
>
>
> On Fri, Jan 20, 2012 at 9:05 AM, Andrew Davis
> <an...@gmail.com>wrote:
>
> > Paul,
> >
> > Our team is reviewing the list of open JIRAs as requested, and I think
> we
> > will have a response back to you on Monday or tuesday.
> >
> > I think it would be much more predictable for the community and
> dependent
> > products, if we published a schedule for locking down 3.0, with some one
> > or two release candidates planned over a few weeks, as I suspect many
> > team's like ours have been in active development and need some time to
> > review test coverage before we declare a 3.0 GA.
> >
> > Aside from the 3.0 immediate release, it would also be helpful to
> publish a
> > regular release plan, maybe with a fixed annual schedule like Eclipse?
> > Thoughts?
> >
> > --Andrew Davis
> > IBM
> >
> > On Fri, Jan 20, 2012 at 9:55 AM, Paul Lindner <li...@inuus.com> wrote:
> >
> > > I'm not keen on version numbers myself.
> > >
> > > We can release at any time really, code is stable, tests are all
> green.
> > >
> > > If someone wants to sign up to do maint releases of 3.0.x that would
> be
> > > helpful.
> > >
> > > Vote:
> > > Release current trunk as shindig-3.0.0, move trunk to 3.1.0-SNAPSHOT
> > >
> > > [ ] +1 do it
> > > [ ] +0 meh
> > > [ ] -1 I have just one more patch.
> > >
> > > If you do -1 please provide code-review links or jira issues you
> consider
> > > blockers for 3.0.0
> > >
> > > On Fri, Jan 20, 2012 at 3:51 AM, Derek Houghton <de...@chuwori.co.uk>
> > > wrote:
> > >
> > > > Hi,
> > > > Didn't catch a reply to this?
> > > > Could you tell me when stable shindig 3.0 is due for public release?
> > > >
> > > > Thanks
> > > > Derek
> > > >
> > > >
> > > > On 16 Jan 2012, at 10:57, Evgeny Bogdanov wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > when the shindig 3.0 is due?
> > > > >
> > > > > Best
> > > > > Evgeny
> > > >
> > > >
> > >
> > >
> > > --
> > > Paul Lindner -- lindner@inuus.com -- profiles.google.com/pmlindner
> > >
> >
>
>
>
> --
> Paul Lindner -- lindner@inuus.com -- profiles.google.com/pmlindner
>
>
--
Paul Lindner -- lindner@inuus.com -- profiles.google.com/pmlindner
Re: Shindig 3.0 timeline
Posted by Dan Dumont <dd...@us.ibm.com>.
Paul,
I'd like to address some of the JIRAs (close or reassign), but it appears
that I cannot modify or close JIRAs that I have not created.
Is there a way for me to get this power? Or do I need to hunt down the
people who created them and ask them to assign them or close them?
From: Paul Lindner <li...@inuus.com>
To: dev@shindig.apache.org, aed13@cornell.edu,
Date: 01/25/2012 03:57 AM
Subject: Re: Shindig 3.0 timeline
Hi Folks.
I started a little housekeeping for 3.0.0:
http://goo.gl/cBNk0
Please add or modify bugs so we only have release blockers that have a
definitive fix. Feel free to bump to 3.1.0 which is the next version we
can work on.
If you need/want higher-level Jira access let me know.
On Fri, Jan 20, 2012 at 9:05 AM, Andrew Davis
<an...@gmail.com>wrote:
> Paul,
>
> Our team is reviewing the list of open JIRAs as requested, and I think
we
> will have a response back to you on Monday or tuesday.
>
> I think it would be much more predictable for the community and
dependent
> products, if we published a schedule for locking down 3.0, with some one
> or two release candidates planned over a few weeks, as I suspect many
> team's like ours have been in active development and need some time to
> review test coverage before we declare a 3.0 GA.
>
> Aside from the 3.0 immediate release, it would also be helpful to
publish a
> regular release plan, maybe with a fixed annual schedule like Eclipse?
> Thoughts?
>
> --Andrew Davis
> IBM
>
> On Fri, Jan 20, 2012 at 9:55 AM, Paul Lindner <li...@inuus.com> wrote:
>
> > I'm not keen on version numbers myself.
> >
> > We can release at any time really, code is stable, tests are all
green.
> >
> > If someone wants to sign up to do maint releases of 3.0.x that would
be
> > helpful.
> >
> > Vote:
> > Release current trunk as shindig-3.0.0, move trunk to 3.1.0-SNAPSHOT
> >
> > [ ] +1 do it
> > [ ] +0 meh
> > [ ] -1 I have just one more patch.
> >
> > If you do -1 please provide code-review links or jira issues you
consider
> > blockers for 3.0.0
> >
> > On Fri, Jan 20, 2012 at 3:51 AM, Derek Houghton <de...@chuwori.co.uk>
> > wrote:
> >
> > > Hi,
> > > Didn't catch a reply to this?
> > > Could you tell me when stable shindig 3.0 is due for public release?
> > >
> > > Thanks
> > > Derek
> > >
> > >
> > > On 16 Jan 2012, at 10:57, Evgeny Bogdanov wrote:
> > >
> > > > Hello,
> > > >
> > > > when the shindig 3.0 is due?
> > > >
> > > > Best
> > > > Evgeny
> > >
> > >
> >
> >
> > --
> > Paul Lindner -- lindner@inuus.com -- profiles.google.com/pmlindner
> >
>
--
Paul Lindner -- lindner@inuus.com -- profiles.google.com/pmlindner
Re: Shindig 3.0 timeline
Posted by Paul Lindner <li...@inuus.com>.
Hi Folks.
I started a little housekeeping for 3.0.0:
http://goo.gl/cBNk0
Please add or modify bugs so we only have release blockers that have a
definitive fix. Feel free to bump to 3.1.0 which is the next version we
can work on.
If you need/want higher-level Jira access let me know.
On Fri, Jan 20, 2012 at 9:05 AM, Andrew Davis <an...@gmail.com>wrote:
> Paul,
>
> Our team is reviewing the list of open JIRAs as requested, and I think we
> will have a response back to you on Monday or tuesday.
>
> I think it would be much more predictable for the community and dependent
> products, if we published a schedule for locking down 3.0, with some one
> or two release candidates planned over a few weeks, as I suspect many
> team's like ours have been in active development and need some time to
> review test coverage before we declare a 3.0 GA.
>
> Aside from the 3.0 immediate release, it would also be helpful to publish a
> regular release plan, maybe with a fixed annual schedule like Eclipse?
> Thoughts?
>
> --Andrew Davis
> IBM
>
> On Fri, Jan 20, 2012 at 9:55 AM, Paul Lindner <li...@inuus.com> wrote:
>
> > I'm not keen on version numbers myself.
> >
> > We can release at any time really, code is stable, tests are all green.
> >
> > If someone wants to sign up to do maint releases of 3.0.x that would be
> > helpful.
> >
> > Vote:
> > Release current trunk as shindig-3.0.0, move trunk to 3.1.0-SNAPSHOT
> >
> > [ ] +1 do it
> > [ ] +0 meh
> > [ ] -1 I have just one more patch.
> >
> > If you do -1 please provide code-review links or jira issues you consider
> > blockers for 3.0.0
> >
> > On Fri, Jan 20, 2012 at 3:51 AM, Derek Houghton <de...@chuwori.co.uk>
> > wrote:
> >
> > > Hi,
> > > Didn't catch a reply to this?
> > > Could you tell me when stable shindig 3.0 is due for public release?
> > >
> > > Thanks
> > > Derek
> > >
> > >
> > > On 16 Jan 2012, at 10:57, Evgeny Bogdanov wrote:
> > >
> > > > Hello,
> > > >
> > > > when the shindig 3.0 is due?
> > > >
> > > > Best
> > > > Evgeny
> > >
> > >
> >
> >
> > --
> > Paul Lindner -- lindner@inuus.com -- profiles.google.com/pmlindner
> >
>
--
Paul Lindner -- lindner@inuus.com -- profiles.google.com/pmlindner
Re: Shindig 3.0 timeline
Posted by Andrew Davis <an...@gmail.com>.
Paul,
Our team is reviewing the list of open JIRAs as requested, and I think we
will have a response back to you on Monday or tuesday.
I think it would be much more predictable for the community and dependent
products, if we published a schedule for locking down 3.0, with some one
or two release candidates planned over a few weeks, as I suspect many
team's like ours have been in active development and need some time to
review test coverage before we declare a 3.0 GA.
Aside from the 3.0 immediate release, it would also be helpful to publish a
regular release plan, maybe with a fixed annual schedule like Eclipse?
Thoughts?
--Andrew Davis
IBM
On Fri, Jan 20, 2012 at 9:55 AM, Paul Lindner <li...@inuus.com> wrote:
> I'm not keen on version numbers myself.
>
> We can release at any time really, code is stable, tests are all green.
>
> If someone wants to sign up to do maint releases of 3.0.x that would be
> helpful.
>
> Vote:
> Release current trunk as shindig-3.0.0, move trunk to 3.1.0-SNAPSHOT
>
> [ ] +1 do it
> [ ] +0 meh
> [ ] -1 I have just one more patch.
>
> If you do -1 please provide code-review links or jira issues you consider
> blockers for 3.0.0
>
> On Fri, Jan 20, 2012 at 3:51 AM, Derek Houghton <de...@chuwori.co.uk>
> wrote:
>
> > Hi,
> > Didn't catch a reply to this?
> > Could you tell me when stable shindig 3.0 is due for public release?
> >
> > Thanks
> > Derek
> >
> >
> > On 16 Jan 2012, at 10:57, Evgeny Bogdanov wrote:
> >
> > > Hello,
> > >
> > > when the shindig 3.0 is due?
> > >
> > > Best
> > > Evgeny
> >
> >
>
>
> --
> Paul Lindner -- lindner@inuus.com -- profiles.google.com/pmlindner
>
RE: Shindig 3.0 timeline
Posted by "Shtein, Ilya" <Il...@fisglobal.com>.
Hi Dennis,
I submitted a defect to Open Ajax bug tracker, as you requested (ID: 3479818, https://sourceforge.net/tracker/?func=detail&atid=874168&aid=3479818&group_id=175671).
Please let me know what I should expect next.
Thanks,
Ilya
From: Dennis Ju [mailto:dennis.ju@liferay.com]
Sent: Wednesday, January 25, 2012 4:17 PM
To: Shtein, Ilya
Cc: dev@shindig.apache.org
Subject: Re: Shindig 3.0 timeline
Hi Ilya,
Your fix looks good, but my concern is that the code change is for OpenAjax Hub's iframe.js. Ideally, we would patch it in OpenAjax's repo and bring in the patched version to Shindig's trunk. Otherwise any patch will be lost when Shindig updates OpenAjax Hub (which should be done anyways since 2.0.7 is out and Shindig is on 2.0.5).
Are you able to create an issue (per your company's policies) on OpenAjax's bug tracker (link<http://sourceforge.net/tracker/?group_id=175671&atid=874168>)? If not, I can do it. Once it's patched there, I can create a patch for Shindig.
Also, what version of Shindig are you testing against? Looking at current trunk's rpc.js changes, it appears that the code changes Maxwell and I suggested in SHINDIG-1497 are no longer necessary in Shindig 3.x, but I haven't tested it myself yet.
Thanks,
Dennis
On Wed, Jan 25, 2012 at 11:48 AM, Shtein, Ilya <Il...@fisglobal.com>> wrote:
My company discourages contributing to open source, so I contributed my fix indirectly by submitting a comment to Dennis's original post. The SHINDIG-1497 issue consists of two parts:
- exceptions when moving pubsub-2 gadget's IFrame in the DOM tree
- problem with multiplying number of subscriptions when dropping a pubsub-2 gadget
My patch takes care of the second issue; Dennis seems to have an idea how to fix the first one (I myself had to use both changes suggested in the discussion between Dennis and Maxwell Chiareli). Or, perhaps the original contributors of pubsub-2 code (Javier Pedemonte, Han Nguyen?) could chime in on what the best route is. Anyway, I give my permission to whoever prepares a patch for SHINDIG-1497 to use the fix I suggested, and hope the issue will be fixed in the upcoming Shindig release.
Thanks,
Ilya
From: Ryan J Baxter [mailto:rjbaxter@us.ibm.com<ma...@us.ibm.com>]
Sent: Tuesday, January 24, 2012 8:52 PM
To: dev@shindig.apache.org<ma...@shindig.apache.org>
Subject: RE: Shindig 3.0 timeline
Ilya, if you or Dennis want to investigate and come up with a patch to support this use case, we are happy to accept it :) Everyone on the dev list would be happy to help you or anyone else through the process of writing the patch and getting it committed.
Regards,
RYAN J. BAXTER
Software Engineer - OpenSocial
IBM Collaboration Solutions
________________________________
Phone: 1-978-899-3041<tel:1-978-899-3041>
E-mail: rjbaxter@us.ibm.com<ma...@us.ibm.com>
Blog: ryanjbaxter.com<http://ryanjbaxter.com/>
Chat: rbaxter85 ryanjasonbaxter
Find me on: and within IBM on: <http://www.linkedin.com/in/ryanjbaxter>
550 King St
Littleton, MA 01460-1250
United States
From: "Shtein, Ilya" <Il...@fisglobal.com>
To: "dev@shindig.apache.org" <de...@shindig.apache.org>,
Date: 01/20/2012 10:12 AM
Subject: RE: Shindig 3.0 timeline
________________________________
Any chance SHINDIG-1497 will be fixed in 3.0.0 (https://issues.apache.org/jira/browse/SHINDIG-1497)? How can a new version be released with such an important feature (pubsub-2) in a broken state? I am not allowed to contribute, but will be happy to provide information to anyone who is willing to work on it.
Thanks,
Ilya
-----Original Message-----
From: Paul Lindner [mailto:lindner@inuus.com]
Sent: Friday, January 20, 2012 8:55 AM
To: dev@shindig.apache.org
Subject: Re: Shindig 3.0 timeline
I'm not keen on version numbers myself.
We can release at any time really, code is stable, tests are all green.
If someone wants to sign up to do maint releases of 3.0.x that would be helpful.
Vote:
Release current trunk as shindig-3.0.0, move trunk to 3.1.0-SNAPSHOT
[ ] +1 do it
[ ] +0 meh
[ ] -1 I have just one more patch.
If you do -1 please provide code-review links or jira issues you consider blockers for 3.0.0
On Fri, Jan 20, 2012 at 3:51 AM, Derek Houghton <de...@chuwori.co.uk> wrote:
> Hi,
> Didn't catch a reply to this?
> Could you tell me when stable shindig 3.0 is due for public release?
>
> Thanks
> Derek
>
>
> On 16 Jan 2012, at 10:57, Evgeny Bogdanov wrote:
>
> > Hello,
> >
> > when the shindig 3.0 is due?
> >
> > Best
> > Evgeny
>
>
--
Paul Lindner -- lindner@inuus.com -- profiles.google.com/pmlindner
_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.<http://www.linkedin.com/in/ryanjbaxter>
<http://www.linkedin.com/in/ryanjbaxter>
<http://www.linkedin.com/in/ryanjbaxter>
--
Nordic Symposium
25 April 2012
Register today: www.liferay.com/nordic2012<http://www.linkedin.com/in/ryanjbaxter>
_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
RE: Shindig 3.0 timeline
Posted by "Shtein, Ilya" <Il...@fisglobal.com>.
Hi Dennis,
I think I can create an issue on OpenAjax's bug tracker. I am testing against the "official" released version of Shindig, which is 2.0 I think (I replaced OpenAjax 2.0.4 in it with OpenAjax 2.0.5 due to a bug that was fixed in 2.0.5). Didn't have a chance to play with 3.x yet...
I will let you know as soon as the issue is created.
Thanks,
Ilya
From: Dennis Ju [mailto:dennis.ju@liferay.com]
Sent: Wednesday, January 25, 2012 4:17 PM
To: Shtein, Ilya
Cc: dev@shindig.apache.org
Subject: Re: Shindig 3.0 timeline
Hi Ilya,
Your fix looks good, but my concern is that the code change is for OpenAjax Hub's iframe.js. Ideally, we would patch it in OpenAjax's repo and bring in the patched version to Shindig's trunk. Otherwise any patch will be lost when Shindig updates OpenAjax Hub (which should be done anyways since 2.0.7 is out and Shindig is on 2.0.5).
Are you able to create an issue (per your company's policies) on OpenAjax's bug tracker (link<http://sourceforge.net/tracker/?group_id=175671&atid=874168>)? If not, I can do it. Once it's patched there, I can create a patch for Shindig.
Also, what version of Shindig are you testing against? Looking at current trunk's rpc.js changes, it appears that the code changes Maxwell and I suggested in SHINDIG-1497 are no longer necessary in Shindig 3.x, but I haven't tested it myself yet.
Thanks,
Dennis
On Wed, Jan 25, 2012 at 11:48 AM, Shtein, Ilya <Il...@fisglobal.com>> wrote:
My company discourages contributing to open source, so I contributed my fix indirectly by submitting a comment to Dennis's original post. The SHINDIG-1497 issue consists of two parts:
- exceptions when moving pubsub-2 gadget's IFrame in the DOM tree
- problem with multiplying number of subscriptions when dropping a pubsub-2 gadget
My patch takes care of the second issue; Dennis seems to have an idea how to fix the first one (I myself had to use both changes suggested in the discussion between Dennis and Maxwell Chiareli). Or, perhaps the original contributors of pubsub-2 code (Javier Pedemonte, Han Nguyen?) could chime in on what the best route is. Anyway, I give my permission to whoever prepares a patch for SHINDIG-1497 to use the fix I suggested, and hope the issue will be fixed in the upcoming Shindig release.
Thanks,
Ilya
From: Ryan J Baxter [mailto:rjbaxter@us.ibm.com<ma...@us.ibm.com>]
Sent: Tuesday, January 24, 2012 8:52 PM
To: dev@shindig.apache.org<ma...@shindig.apache.org>
Subject: RE: Shindig 3.0 timeline
Ilya, if you or Dennis want to investigate and come up with a patch to support this use case, we are happy to accept it :) Everyone on the dev list would be happy to help you or anyone else through the process of writing the patch and getting it committed.
Regards,
RYAN J. BAXTER
Software Engineer - OpenSocial
IBM Collaboration Solutions
________________________________
Phone: 1-978-899-3041<tel:1-978-899-3041>
E-mail: rjbaxter@us.ibm.com<ma...@us.ibm.com>
Blog: ryanjbaxter.com<http://ryanjbaxter.com/>
Chat: rbaxter85 ryanjasonbaxter
Find me on: and within IBM on: <http://www.linkedin.com/in/ryanjbaxter>
550 King St
Littleton, MA 01460-1250
United States
From: "Shtein, Ilya" <Il...@fisglobal.com>
To: "dev@shindig.apache.org" <de...@shindig.apache.org>,
Date: 01/20/2012 10:12 AM
Subject: RE: Shindig 3.0 timeline
________________________________
Any chance SHINDIG-1497 will be fixed in 3.0.0 (https://issues.apache.org/jira/browse/SHINDIG-1497)? How can a new version be released with such an important feature (pubsub-2) in a broken state? I am not allowed to contribute, but will be happy to provide information to anyone who is willing to work on it.
Thanks,
Ilya
-----Original Message-----
From: Paul Lindner [mailto:lindner@inuus.com]
Sent: Friday, January 20, 2012 8:55 AM
To: dev@shindig.apache.org
Subject: Re: Shindig 3.0 timeline
I'm not keen on version numbers myself.
We can release at any time really, code is stable, tests are all green.
If someone wants to sign up to do maint releases of 3.0.x that would be helpful.
Vote:
Release current trunk as shindig-3.0.0, move trunk to 3.1.0-SNAPSHOT
[ ] +1 do it
[ ] +0 meh
[ ] -1 I have just one more patch.
If you do -1 please provide code-review links or jira issues you consider blockers for 3.0.0
On Fri, Jan 20, 2012 at 3:51 AM, Derek Houghton <de...@chuwori.co.uk> wrote:
> Hi,
> Didn't catch a reply to this?
> Could you tell me when stable shindig 3.0 is due for public release?
>
> Thanks
> Derek
>
>
> On 16 Jan 2012, at 10:57, Evgeny Bogdanov wrote:
>
> > Hello,
> >
> > when the shindig 3.0 is due?
> >
> > Best
> > Evgeny
>
>
--
Paul Lindner -- lindner@inuus.com -- profiles.google.com/pmlindner
_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.<http://www.linkedin.com/in/ryanjbaxter>
<http://www.linkedin.com/in/ryanjbaxter>
<http://www.linkedin.com/in/ryanjbaxter>
--
Nordic Symposium
25 April 2012
Register today: www.liferay.com/nordic2012<http://www.linkedin.com/in/ryanjbaxter>
_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
Re: Shindig 3.0 timeline
Posted by Dennis Ju <de...@liferay.com>.
Hi Ilya,
Your fix looks good, but my concern is that the code change is for OpenAjax
Hub's iframe.js. Ideally, we would patch it in OpenAjax's repo and bring in
the patched version to Shindig's trunk. Otherwise any patch will be lost
when Shindig updates OpenAjax Hub (which should be done anyways since 2.0.7
is out and Shindig is on 2.0.5).
Are you able to create an issue (per your company's policies) on OpenAjax's
bug tracker (link<http://sourceforge.net/tracker/?group_id=175671&atid=874168>)?
If not, I can do it. Once it's patched there, I can create a patch for
Shindig.
Also, what version of Shindig are you testing against? Looking at current
trunk's rpc.js changes, it appears that the code changes Maxwell and I
suggested in SHINDIG-1497 are no longer necessary in Shindig 3.x, but I
haven't tested it myself yet.
Thanks,
Dennis
On Wed, Jan 25, 2012 at 11:48 AM, Shtein, Ilya <Il...@fisglobal.com>wrote:
> My company discourages contributing to open source, so I contributed my
> fix indirectly by submitting a comment to Dennis’s original post. The
> SHINDIG-1497 issue consists of two parts:****
>
> **- **exceptions when moving pubsub-2 gadget’s IFrame in the DOM
> tree****
>
> **- **problem with multiplying number of subscriptions when
> dropping a pubsub-2 gadget****
>
> My patch takes care of the second issue; Dennis seems to have an idea how
> to fix the first one (I myself had to use both changes suggested in the
> discussion between Dennis and Maxwell Chiareli). Or, perhaps the original
> contributors of pubsub-2 code (Javier Pedemonte, Han Nguyen?) could chime
> in on what the best route is. Anyway, I give my permission to whoever
> prepares a patch for SHINDIG-1497 to use the fix I suggested, and hope the
> issue will be fixed in the upcoming Shindig release.****
>
> ** **
>
> Thanks,****
>
> Ilya****
>
> ** **
>
> *From:* Ryan J Baxter [mailto:rjbaxter@us.ibm.com]
> *Sent:* Tuesday, January 24, 2012 8:52 PM
> *To:* dev@shindig.apache.org
>
> *Subject:* RE: Shindig 3.0 timeline****
>
> ** **
>
> Ilya, if you or Dennis want to investigate and come up with a patch to
> support this use case, we are happy to accept it :) Everyone on the dev
> list would be happy to help you or anyone else through the process of
> writing the patch and getting it committed.
>
>
> Regards,
>
> *RYAN J. BAXTER*
> Software Engineer - OpenSocial
> IBM Collaboration Solutions ****
> ------------------------------
>
> *Phone:* 1-978-899-3041*
> E-mail:* rjbaxter@us.ibm.com*
> Blog: *ryanjbaxter.com*
> Chat:*[image: Google Talk:] rbaxter85 [image: Skype:]ryanjasonbaxter *
> Find me on:* [image: LinkedIn: http://www.linkedin.com/in/ryanjbaxter]<http://www.linkedin.com/in/ryanjbaxter>
> [image: Twitter: http://twitter.com/ryanjbaxter]<http://twitter.com/ryanjbaxter> [image:
> Blog RSS: http://ryanjbaxter.com/feed/] <http://ryanjbaxter.com/feed/> [image:
> Facebook: http://www.facebook.com/profile.php?id=1807077]<http://www.facebook.com/profile.php?id=1807077> [image:
> GooglePlus: https://plus.google.com/u/0/113940278097622367914]<https://plus.google.com/u/0/113940278097622367914>
> *and within IBM on:* [image: Lotus Connections:
> https://w3-connections.ibm.com/profiles/html/profileView.do?userid=a20c3c40-ac79-102c-85c8-d8c2f5822a71&lang=en_us]<https://w3-connections.ibm.com/profiles/html/profileView.do?userid=a20c3c40-ac79-102c-85c8-d8c2f5822a71&lang=en_us>
> ****
>
> [image: IBM]
>
> 550 King St
> Littleton, MA 01460-1250
> United States****
>
>
>
>
>
>
>
> From: "Shtein, Ilya" <Il...@fisglobal.com>
> To: "dev@shindig.apache.org" <de...@shindig.apache.org>,
> Date: 01/20/2012 10:12 AM
> Subject: RE: Shindig 3.0 timeline ****
> ------------------------------
>
>
>
>
> Any chance SHINDIG-1497 will be fixed in 3.0.0 (
> https://issues.apache.org/jira/browse/SHINDIG-1497)? How can a new
> version be released with such an important feature (pubsub-2) in a broken
> state? I am not allowed to contribute, but will be happy to provide
> information to anyone who is willing to work on it.
>
> Thanks,
> Ilya
>
> -----Original Message-----
> From: Paul Lindner [mailto:lindner@inuus.com <li...@inuus.com>]
> Sent: Friday, January 20, 2012 8:55 AM
> To: dev@shindig.apache.org
> Subject: Re: Shindig 3.0 timeline
>
> I'm not keen on version numbers myself.
>
> We can release at any time really, code is stable, tests are all green.
>
> If someone wants to sign up to do maint releases of 3.0.x that would be
> helpful.
>
> Vote:
> Release current trunk as shindig-3.0.0, move trunk to 3.1.0-SNAPSHOT
>
> [ ] +1 do it
> [ ] +0 meh
> [ ] -1 I have just one more patch.
>
> If you do -1 please provide code-review links or jira issues you consider
> blockers for 3.0.0
>
> On Fri, Jan 20, 2012 at 3:51 AM, Derek Houghton <de...@chuwori.co.uk>
> wrote:
>
> > Hi,
> > Didn't catch a reply to this?
> > Could you tell me when stable shindig 3.0 is due for public release?
> >
> > Thanks
> > Derek
> >
> >
> > On 16 Jan 2012, at 10:57, Evgeny Bogdanov wrote:
> >
> > > Hello,
> > >
> > > when the shindig 3.0 is due?
> > >
> > > Best
> > > Evgeny
> >
> >
>
>
> --
> Paul Lindner -- lindner@inuus.com -- profiles.google.com/pmlindner
>
> _____________
> The information contained in this message is proprietary and/or
> confidential. If you are not the intended recipient, please: (i) delete the
> message and all copies; (ii) do not disclose, distribute or use the message
> in any manner; and (iii) notify the sender immediately. In addition, please
> be aware that any message addressed to our domain is subject to archiving
> and review by persons other than the intended recipient. Thank you.****
> _____________
> The information contained in this message is proprietary and/or
> confidential. If you are not the intended recipient, please: (i) delete the
> message and all copies; (ii) do not disclose, distribute or use the message
> in any manner; and (iii) notify the sender immediately. In addition, please
> be aware that any message addressed to our domain is subject to archiving
> and review by persons other than the intended recipient. Thank you.
>
--
*Nordic Symposium*
25 April 2012
Register today: www.liferay.com/nordic2012
RE: Shindig 3.0 timeline
Posted by "Shtein, Ilya" <Il...@fisglobal.com>.
My company discourages contributing to open source, so I contributed my fix indirectly by submitting a comment to Dennis's original post. The SHINDIG-1497 issue consists of two parts:
- exceptions when moving pubsub-2 gadget's IFrame in the DOM tree
- problem with multiplying number of subscriptions when dropping a pubsub-2 gadget
My patch takes care of the second issue; Dennis seems to have an idea how to fix the first one (I myself had to use both changes suggested in the discussion between Dennis and Maxwell Chiareli). Or, perhaps the original contributors of pubsub-2 code (Javier Pedemonte, Han Nguyen?) could chime in on what the best route is. Anyway, I give my permission to whoever prepares a patch for SHINDIG-1497 to use the fix I suggested, and hope the issue will be fixed in the upcoming Shindig release.
Thanks,
Ilya
From: Ryan J Baxter [mailto:rjbaxter@us.ibm.com]
Sent: Tuesday, January 24, 2012 8:52 PM
To: dev@shindig.apache.org
Subject: RE: Shindig 3.0 timeline
Ilya, if you or Dennis want to investigate and come up with a patch to support this use case, we are happy to accept it :) Everyone on the dev list would be happy to help you or anyone else through the process of writing the patch and getting it committed.
Regards,
RYAN J. BAXTER
Software Engineer - OpenSocial
IBM Collaboration Solutions
________________________________
Phone: 1-978-899-3041
E-mail: rjbaxter@us.ibm.com<ma...@us.ibm.com>
Blog: ryanjbaxter.com<http://ryanjbaxter.com/>
Chat:[Google Talk:] rbaxter85 [Skype:] ryanjasonbaxter
Find me on: [LinkedIn: http://www.linkedin.com/in/ryanjbaxter] <http://www.linkedin.com/in/ryanjbaxter> [Twitter: http://twitter.com/ryanjbaxter] <http://twitter.com/ryanjbaxter> [Blog RSS: http://ryanjbaxter.com/feed/] <http://ryanjbaxter.com/feed/> [Facebook: http://www.facebook.com/profile.php?id=1807077] <http://www.facebook.com/profile.php?id=1807077> [GooglePlus: https://plus.google.com/u/0/113940278097622367914] <https://plus.google.com/u/0/113940278097622367914> and within IBM on: [Lotus Connections: https://w3-connections.ibm.com/profiles/html/profileView.do?userid=a20c3c40-ac79-102c-85c8-d8c2f5822a71&lang=en_us] <https://w3-connections.ibm.com/profiles/html/profileView.do?userid=a20c3c40-ac79-102c-85c8-d8c2f5822a71&lang=en_us>
[IBM]
550 King St
Littleton, MA 01460-1250
United States
From: "Shtein, Ilya" <Il...@fisglobal.com>>
To: "dev@shindig.apache.org<ma...@shindig.apache.org>" <de...@shindig.apache.org>>,
Date: 01/20/2012 10:12 AM
Subject: RE: Shindig 3.0 timeline
________________________________
Any chance SHINDIG-1497 will be fixed in 3.0.0 (https://issues.apache.org/jira/browse/SHINDIG-1497)? How can a new version be released with such an important feature (pubsub-2) in a broken state? I am not allowed to contribute, but will be happy to provide information to anyone who is willing to work on it.
Thanks,
Ilya
-----Original Message-----
From: Paul Lindner [mailto:lindner@inuus.com]
Sent: Friday, January 20, 2012 8:55 AM
To: dev@shindig.apache.org<ma...@shindig.apache.org>
Subject: Re: Shindig 3.0 timeline
I'm not keen on version numbers myself.
We can release at any time really, code is stable, tests are all green.
If someone wants to sign up to do maint releases of 3.0.x that would be helpful.
Vote:
Release current trunk as shindig-3.0.0, move trunk to 3.1.0-SNAPSHOT
[ ] +1 do it
[ ] +0 meh
[ ] -1 I have just one more patch.
If you do -1 please provide code-review links or jira issues you consider blockers for 3.0.0
On Fri, Jan 20, 2012 at 3:51 AM, Derek Houghton <de...@chuwori.co.uk>> wrote:
> Hi,
> Didn't catch a reply to this?
> Could you tell me when stable shindig 3.0 is due for public release?
>
> Thanks
> Derek
>
>
> On 16 Jan 2012, at 10:57, Evgeny Bogdanov wrote:
>
> > Hello,
> >
> > when the shindig 3.0 is due?
> >
> > Best
> > Evgeny
>
>
--
Paul Lindner -- lindner@inuus.com<ma...@inuus.com> -- profiles.google.com/pmlindner
_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
RE: Shindig 3.0 timeline
Posted by Ryan J Baxter <rj...@us.ibm.com>.
Ilya, if you or Dennis want to investigate and come up with a patch to
support this use case, we are happy to accept it :) Everyone on the dev
list would be happy to help you or anyone else through the process of
writing the patch and getting it committed.
Regards,
RYAN J. BAXTER
Software Engineer - OpenSocial
IBM Collaboration Solutions
Phone: 1-978-899-3041
E-mail: rjbaxter@us.ibm.com
Blog: ryanjbaxter.com
Chat: rbaxter85 ryanjasonbaxter
Find me on: and within IBM on:
550 King St
Littleton, MA 01460-1250
United States
From: "Shtein, Ilya" <Il...@fisglobal.com>
To: "dev@shindig.apache.org" <de...@shindig.apache.org>,
Date: 01/20/2012 10:12 AM
Subject: RE: Shindig 3.0 timeline
Any chance SHINDIG-1497 will be fixed in 3.0.0 (
https://issues.apache.org/jira/browse/SHINDIG-1497)? How can a new version
be released with such an important feature (pubsub-2) in a broken state? I
am not allowed to contribute, but will be happy to provide information to
anyone who is willing to work on it.
Thanks,
Ilya
-----Original Message-----
From: Paul Lindner [mailto:lindner@inuus.com]
Sent: Friday, January 20, 2012 8:55 AM
To: dev@shindig.apache.org
Subject: Re: Shindig 3.0 timeline
I'm not keen on version numbers myself.
We can release at any time really, code is stable, tests are all green.
If someone wants to sign up to do maint releases of 3.0.x that would be
helpful.
Vote:
Release current trunk as shindig-3.0.0, move trunk to 3.1.0-SNAPSHOT
[ ] +1 do it
[ ] +0 meh
[ ] -1 I have just one more patch.
If you do -1 please provide code-review links or jira issues you consider
blockers for 3.0.0
On Fri, Jan 20, 2012 at 3:51 AM, Derek Houghton <de...@chuwori.co.uk>
wrote:
> Hi,
> Didn't catch a reply to this?
> Could you tell me when stable shindig 3.0 is due for public release?
>
> Thanks
> Derek
>
>
> On 16 Jan 2012, at 10:57, Evgeny Bogdanov wrote:
>
> > Hello,
> >
> > when the shindig 3.0 is due?
> >
> > Best
> > Evgeny
>
>
--
Paul Lindner -- lindner@inuus.com -- profiles.google.com/pmlindner
_____________
The information contained in this message is proprietary and/or
confidential. If you are not the intended recipient, please: (i) delete
the message and all copies; (ii) do not disclose, distribute or use the
message in any manner; and (iii) notify the sender immediately. In
addition, please be aware that any message addressed to our domain is
subject to archiving and review by persons other than the intended
recipient. Thank you.
RE: Shindig 3.0 timeline
Posted by "Shtein, Ilya" <Il...@fisglobal.com>.
Any chance SHINDIG-1497 will be fixed in 3.0.0 (https://issues.apache.org/jira/browse/SHINDIG-1497)? How can a new version be released with such an important feature (pubsub-2) in a broken state? I am not allowed to contribute, but will be happy to provide information to anyone who is willing to work on it.
Thanks,
Ilya
-----Original Message-----
From: Paul Lindner [mailto:lindner@inuus.com]
Sent: Friday, January 20, 2012 8:55 AM
To: dev@shindig.apache.org
Subject: Re: Shindig 3.0 timeline
I'm not keen on version numbers myself.
We can release at any time really, code is stable, tests are all green.
If someone wants to sign up to do maint releases of 3.0.x that would be helpful.
Vote:
Release current trunk as shindig-3.0.0, move trunk to 3.1.0-SNAPSHOT
[ ] +1 do it
[ ] +0 meh
[ ] -1 I have just one more patch.
If you do -1 please provide code-review links or jira issues you consider blockers for 3.0.0
On Fri, Jan 20, 2012 at 3:51 AM, Derek Houghton <de...@chuwori.co.uk> wrote:
> Hi,
> Didn't catch a reply to this?
> Could you tell me when stable shindig 3.0 is due for public release?
>
> Thanks
> Derek
>
>
> On 16 Jan 2012, at 10:57, Evgeny Bogdanov wrote:
>
> > Hello,
> >
> > when the shindig 3.0 is due?
> >
> > Best
> > Evgeny
>
>
--
Paul Lindner -- lindner@inuus.com -- profiles.google.com/pmlindner
_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
Re: Shindig 3.0 timeline
Posted by Paul Lindner <li...@inuus.com>.
I'm not keen on version numbers myself.
We can release at any time really, code is stable, tests are all green.
If someone wants to sign up to do maint releases of 3.0.x that would be
helpful.
Vote:
Release current trunk as shindig-3.0.0, move trunk to 3.1.0-SNAPSHOT
[ ] +1 do it
[ ] +0 meh
[ ] -1 I have just one more patch.
If you do -1 please provide code-review links or jira issues you consider
blockers for 3.0.0
On Fri, Jan 20, 2012 at 3:51 AM, Derek Houghton <de...@chuwori.co.uk> wrote:
> Hi,
> Didn't catch a reply to this?
> Could you tell me when stable shindig 3.0 is due for public release?
>
> Thanks
> Derek
>
>
> On 16 Jan 2012, at 10:57, Evgeny Bogdanov wrote:
>
> > Hello,
> >
> > when the shindig 3.0 is due?
> >
> > Best
> > Evgeny
>
>
--
Paul Lindner -- lindner@inuus.com -- profiles.google.com/pmlindner
Re: Shindig 3.0 timeline
Posted by Derek Houghton <de...@chuwori.co.uk>.
Hi,
Didn't catch a reply to this?
Could you tell me when stable shindig 3.0 is due for public release?
Thanks
Derek
On 16 Jan 2012, at 10:57, Evgeny Bogdanov wrote:
> Hello,
>
> when the shindig 3.0 is due?
>
> Best
> Evgeny
Shindig 3.0 timeline
Posted by Evgeny Bogdanov <ev...@epfl.ch>.
Hello,
when the shindig 3.0 is due?
Best
Evgeny
Re: Allowing an authorization server to provide an updated scope for
OAuth2 tokens
Posted by Michael Matthews <ma...@oclc.org>.
Hi Matthew,
I think the usecase where gadgets can see the scope that was granted is
useful, but it¹s not what we had in mind.
Our use case is an application where a user authenticates and is associated
with an institution. It¹s possible for a user to login with a different
institution context later. For example, the user may initially login and use
our UI in the context of Institution 1 and then later login and use the UI
in the context of Institution 2. In this scenario, we want to avoid reuse
of an access token, issued by our authorization server, that was issued to
the user when they were in the context of Institution 1. To do this, we are
considering making our authorization server issue the access token with an
updated scope value.
I haven¹t figured this piece out yet, but we¹d have to provide a custom
implementation of one of Shindig¹s OAuth2 request handlers to modify the
scope when checking to see if an access token already exists in the
OAuth2Store.
Mike
On 1/14/12 10:45 PM, "Matthew G Marum" <mg...@us.ibm.com> wrote:
> Hi Mike,
>
> I agree with your reading of the OAuth 2 spec. The scope of the access
> token that is granted to the consumer does not have to be the same as what
> was requested.
>
> I think gadgets need to be able to see the scope that was granted in order
> to cleanly handle situations were they have access to some but not all the
> requested resources. Is this the use case that you had in mind?
>
> Matthew G Marum
> Software Engineer | IBM Software Emerging Standards
> mgmarum@us.ibm.com | Office: 1 919 254 9702
>
>
> |------------>
> | From: |
> |------------>
>>
>> >----------------------------------------------------------------------------
>> -----------------------------------------------------------------|
> |Michael Matthews <ma...@oclc.org>
> |
>>
>> >----------------------------------------------------------------------------
>> -----------------------------------------------------------------|
> |------------>
> | To: |
> |------------>
>>
>> >----------------------------------------------------------------------------
>> -----------------------------------------------------------------|
> |"dev@shindig.apache.org" <de...@shindig.apache.org>
> |
>>
>> >----------------------------------------------------------------------------
>> -----------------------------------------------------------------|
> |------------>
> | Date: |
> |------------>
>>
>> >----------------------------------------------------------------------------
>> -----------------------------------------------------------------|
> |01/13/2012 02:01 PM
> |
>>
>> >----------------------------------------------------------------------------
>> -----------------------------------------------------------------|
> |------------>
> | Subject: |
> |------------>
>>
>> >----------------------------------------------------------------------------
>> -----------------------------------------------------------------|
> |Allowing an authorization server to provide an updated scope for OAuth2
> tokens |
>>
>> >----------------------------------------------------------------------------
>> -----------------------------------------------------------------|
>
>
>
>
>
> Section 3.3 [1] of the OAuth2 spec suggests that an authorization server
> may
> issue an access token with a scope different than what was requested. It
> goes on to say that the authorization server SHOULD include a "scope"
> response parameter to inform the client of the actual scope granted.
>
> We'd like to take advantage of this in our internally developed
> authorization server. However it appears that Shindig does not look for
> this
> "scope" parameter in the access token response. It always uses the scope
> specified in the gadget (which is stored in the OAuth2Accessor).
>
> It seems to me that the TokenAuthorizationResponseHandler should check the
> response from the token endpoint to see if it contains an updated scope
> instead of only using the scope from the OAuth2Accessor. Does this seem
> like a reasonable interpretation of the OAuth2 spec? If so, I'd be happy to
> create a JIRA and contribute a patch.
>
> Thanks
> Mike
>
> [1] http://tools.ietf.org/html/draft-ietf-oauth-v2-21#section-3.3
>
>
>
>
>
Re: Allowing an authorization server to provide an updated scope for OAuth2
tokens
Posted by Matthew G Marum <mg...@us.ibm.com>.
Hi Mike,
I agree with your reading of the OAuth 2 spec. The scope of the access
token that is granted to the consumer does not have to be the same as what
was requested.
I think gadgets need to be able to see the scope that was granted in order
to cleanly handle situations were they have access to some but not all the
requested resources. Is this the use case that you had in mind?
Matthew G Marum
Software Engineer | IBM Software Emerging Standards
mgmarum@us.ibm.com | Office: 1 919 254 9702
|------------>
| From: |
|------------>
>---------------------------------------------------------------------------------------------------------------------------------------------|
|Michael Matthews <ma...@oclc.org> |
>---------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>---------------------------------------------------------------------------------------------------------------------------------------------|
|"dev@shindig.apache.org" <de...@shindig.apache.org> |
>---------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>---------------------------------------------------------------------------------------------------------------------------------------------|
|01/13/2012 02:01 PM |
>---------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>---------------------------------------------------------------------------------------------------------------------------------------------|
|Allowing an authorization server to provide an updated scope for OAuth2 tokens |
>---------------------------------------------------------------------------------------------------------------------------------------------|
Section 3.3 [1] of the OAuth2 spec suggests that an authorization server
may
issue an access token with a scope different than what was requested. It
goes on to say that the authorization server SHOULD include a "scope"
response parameter to inform the client of the actual scope granted.
We'd like to take advantage of this in our internally developed
authorization server. However it appears that Shindig does not look for
this
"scope" parameter in the access token response. It always uses the scope
specified in the gadget (which is stored in the OAuth2Accessor).
It seems to me that the TokenAuthorizationResponseHandler should check the
response from the token endpoint to see if it contains an updated scope
instead of only using the scope from the OAuth2Accessor. Does this seem
like a reasonable interpretation of the OAuth2 spec? If so, I'd be happy to
create a JIRA and contribute a patch.
Thanks
Mike
[1] http://tools.ietf.org/html/draft-ietf-oauth-v2-21#section-3.3