https://dev.arvados.org/https://dev.arvados.org/favicon.ico?15576888422019-01-30T19:32:33ZArvadosArvados - Bug #14799: [SSO] bump the omniauth-google-oauth2 gem to 0.6.0https://dev.arvados.org/issues/14799?journal_id=710482019-01-30T19:32:33ZWard Vandewegeward@curii.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/71048/diff?detail_id=68111">diff</a>)</li></ul> Arvados - Bug #14799: [SSO] bump the omniauth-google-oauth2 gem to 0.6.0https://dev.arvados.org/issues/14799?journal_id=710492019-01-30T19:36:41ZTom Morristfmorris@veritasgenetics.com
<ul><li><strong>Target version</strong> set to <i>2019-02-13 Sprint</i></li><li><strong>Release</strong> set to <i>21</i></li></ul> Arvados - Bug #14799: [SSO] bump the omniauth-google-oauth2 gem to 0.6.0https://dev.arvados.org/issues/14799?journal_id=710502019-01-30T19:44:25ZPeter Amstutzpeter.amstutz@curii.com
<ul><li><strong>Assigned To</strong> set to <i>Peter Amstutz</i></li><li><strong>Target version</strong> deleted (<del><i>2019-02-13 Sprint</i></del>)</li><li><strong>Release</strong> deleted (<del><i>21</i></del>)</li></ul> Arvados - Bug #14799: [SSO] bump the omniauth-google-oauth2 gem to 0.6.0https://dev.arvados.org/issues/14799?journal_id=710592019-01-30T21:18:04ZTom Morristfmorris@veritasgenetics.com
<ul><li><strong>Target version</strong> set to <i>2019-02-13 Sprint</i></li><li><strong>Release</strong> set to <i>21</i></li></ul> Arvados - Bug #14799: [SSO] bump the omniauth-google-oauth2 gem to 0.6.0https://dev.arvados.org/issues/14799?journal_id=710902019-02-01T19:19:48ZPeter Amstutzpeter.amstutz@curii.com
<ul></ul><p>14799-google-oauth2-bump @ 3fb33817af5bf4edbaef406936dd6d51b133cc72</p>
<p>Just updates packages in Gemfile.lock</p>
<p>In testing, was able to get a successful google sign-on, but the redirects back to workbench didn't quite work for me. I'm pretty sure it is due to test environment issues -- my development instance doesn't have its own resolvable DNS hostname, and google doesn't let you use an IP address for the authorized callback URI.</p>
<p>Most likely this will either work with no configuration changes (able to continue using existing oauth2 client ids), or only require issuing a new oauth2 client id (if the old google+ scopes are a problem.)</p> Arvados - Bug #14799: [SSO] bump the omniauth-google-oauth2 gem to 0.6.0https://dev.arvados.org/issues/14799?journal_id=710912019-02-01T20:35:13ZWard Vandewegeward@curii.com
<ul></ul><p>Peter Amstutz wrote:</p>
<blockquote>
<p>14799-google-oauth2-bump @ 3fb33817af5bf4edbaef406936dd6d51b133cc72</p>
<p>Just updates packages in Gemfile.lock</p>
<p>In testing, was able to get a successful google sign-on, but the redirects back to workbench didn't quite work for me. I'm pretty sure it is due to test environment issues -- my development instance doesn't have its own resolvable DNS hostname, and google doesn't let you use an IP address for the authorized callback URI.</p>
<p>Most likely this will either work with no configuration changes (able to continue using existing oauth2 client ids), or only require issuing a new oauth2 client id (if the old google+ scopes are a problem.)</p>
</blockquote>
<p>LGTM, tested without issues. Please merge.</p> Arvados - Bug #14799: [SSO] bump the omniauth-google-oauth2 gem to 0.6.0https://dev.arvados.org/issues/14799?journal_id=711012019-02-04T15:52:37ZWard Vandewegeward@curii.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul> Arvados - Bug #14799: [SSO] bump the omniauth-google-oauth2 gem to 0.6.0https://dev.arvados.org/issues/14799?journal_id=711032019-02-04T15:53:08ZWard Vandewegeward@curii.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li></ul>