https://dev.arvados.org/https://dev.arvados.org/favicon.ico?15576888422018-10-18T15:11:15ZArvadosArvados - Bug #14377: [API] 401 on 4xphq with generated tokenhttps://dev.arvados.org/issues/14377?journal_id=679312018-10-18T15:11:15ZLucas Di Pentimalucas.dipentima@curii.com
<ul><li><strong>Subject</strong> changed from <i>401 on 4xphq with generated token</i> to <i>[API] 401 on 4xphq with generated token</i></li><li><strong>Category</strong> set to <i>API</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Target version</strong> set to <i>2018-10-31 sprint</i></li></ul> Arvados - Bug #14377: [API] 401 on 4xphq with generated tokenhttps://dev.arvados.org/issues/14377?journal_id=679322018-10-18T15:17:20ZLucas Di Pentimalucas.dipentima@curii.com
<ul></ul><p>On <a class="issue tracker-2 status-3 priority-4 priority-default closed parent" title="Feature: [API] issues v2 format auth tokens (Resolved)" href="https://dev.arvados.org/issues/14196">#14196</a> we added v2 auth tokens by default. I'm investigating if this could have produced the problem.</p> Arvados - Bug #14377: [API] 401 on 4xphq with generated tokenhttps://dev.arvados.org/issues/14377?journal_id=679402018-10-18T21:02:49ZLucas Di Pentimalucas.dipentima@curii.com
<ul></ul><p>It seems that there's no bug causing this, re-tried with a fresh token and it's running ok.</p> Arvados - Bug #14377: [API] 401 on 4xphq with generated tokenhttps://dev.arvados.org/issues/14377?journal_id=679412018-10-18T21:03:04ZLucas Di Pentimalucas.dipentima@curii.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Closed</i></li></ul> Arvados - Bug #14377: [API] 401 on 4xphq with generated tokenhttps://dev.arvados.org/issues/14377?journal_id=686922018-11-13T20:53:06ZTom Morristfmorris@veritasgenetics.com
<ul><li><strong>Release</strong> set to <i>14</i></li></ul>