https://dev.arvados.org/https://dev.arvados.org/favicon.ico?15576888422019-08-07T14:25:59ZArvadosArvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=767492019-08-07T14:25:59ZPeter Amstutzpeter.amstutz@curii.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=767502019-08-07T14:27:11ZPeter Amstutzpeter.amstutz@curii.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/76750/diff?detail_id=73437">diff</a>)</li><li><strong>Status</strong> changed from <i>In Progress</i> to <i>New</i></li></ul> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=767562019-08-07T14:28:11ZPeter Amstutzpeter.amstutz@curii.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-6 status-3 priority-4 priority-default closed parent" href="/issues/15529">Idea #15529</a>: [API] [Controller] Share user account database with a group of trusted clusters</i> added</li></ul> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=767752019-08-07T17:31:01ZTom Morristfmorris@veritasgenetics.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/76775/diff?detail_id=73465">diff</a>)</li></ul> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=767762019-08-07T17:39:50ZEric Biagiotti
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/76776/diff?detail_id=73466">diff</a>)</li></ul> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=767782019-08-07T17:53:47ZEric Biagiotti
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/76778/diff?detail_id=73468">diff</a>)</li></ul> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=767792019-08-07T18:02:07ZEric Biagiotti
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/76779/diff?detail_id=73469">diff</a>)</li></ul> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=767802019-08-07T18:08:44ZTom Morristfmorris@veritasgenetics.com
<ul><li><strong>Story points</strong> set to <i>2.0</i></li></ul> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=769532019-08-14T14:54:52ZTom Morristfmorris@veritasgenetics.com
<ul><li><strong>Target version</strong> changed from <i>To Be Groomed</i> to <i>2019-08-28 Sprint</i></li></ul> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=769772019-08-14T15:50:48ZTom Morristfmorris@veritasgenetics.com
<ul><li><strong>Target version</strong> changed from <i>2019-08-28 Sprint</i> to <i>Arvados Future Sprints</i></li></ul> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=771272019-08-21T15:40:15ZPeter Amstutzpeter.amstutz@curii.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/77127/diff?detail_id=73798">diff</a>)</li></ul> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=771312019-08-21T16:41:09ZPeter Amstutzpeter.amstutz@curii.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/77131/diff?detail_id=73803">diff</a>)</li></ul> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=775542019-09-11T15:08:42ZTom Morristfmorris@veritasgenetics.com
<ul><li><strong>Target version</strong> changed from <i>Arvados Future Sprints</i> to <i>2019-09-25 Sprint</i></li></ul> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=775562019-09-11T15:09:06ZPeter Amstutzpeter.amstutz@curii.com
<ul><li><strong>Assigned To</strong> set to <i>Peter Amstutz</i></li><li><strong>Target version</strong> changed from <i>2019-09-25 Sprint</i> to <i>Arvados Future Sprints</i></li></ul> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=775592019-09-11T15:13:37ZPeter Amstutzpeter.amstutz@curii.com
<ul><li><strong>Target version</strong> changed from <i>Arvados Future Sprints</i> to <i>2019-09-25 Sprint</i></li></ul> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=775812019-09-11T20:19:08ZPeter Amstutzpeter.amstutz@curii.com
<ul></ul><p>Also weird things happen if configuration changes inconsistently with what's in local storage.</p> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=778362019-09-25T13:56:04ZPeter Amstutzpeter.amstutz@curii.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=778532019-09-25T15:18:01ZPeter Amstutzpeter.amstutz@curii.com
<ul><li><strong>Target version</strong> changed from <i>2019-09-25 Sprint</i> to <i>2019-10-09 Sprint</i></li></ul> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=780992019-10-07T20:22:52ZPeter Amstutzpeter.amstutz@curii.com
<ul></ul><p>workbench2 repository</p>
<p>15530-wb2-logincluster @ <a class="changeset" title="15530: Don't offer to link remote account if LoginCluster is true." href="https://dev.arvados.org/projects/arvados/repository/arvados/revisions/d866a8ad7d9d8f48c761fa7ea8ea96b17cbfdb2f">d866a8ad7d9d8f48c761fa7ea8ea96b17cbfdb2f</a></p>
<p>To test this you need a federation with LoginCluster set, eg the "fedbox" cluster set up to test arv-federation-migrate.</p>
<ul>
<li>wb2 "homecluster" is set to value of logincluster</li>
<li>don't display dropdown to select alternate home cluster for login and linking when logincluster is non-empty</li>
<li>when loading "sessions" from local storage, clear "active" and "validated" flags and re-initialize</li>
<li>when searching and logincluster is set, send unsalted token</li>
<li>when logging into the head logincluster, send unsalted token to other workbenches</li>
</ul> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=781212019-10-09T15:08:03ZPeter Amstutzpeter.amstutz@curii.com
<ul><li><strong>Target version</strong> changed from <i>2019-10-09 Sprint</i> to <i>2019-10-23 Sprint</i></li></ul> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=781772019-10-09T17:55:32ZEric Biagiotti
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-4 priority-default closed" href="/issues/15709">Bug #15709</a>: [Workbench2] Automatically add local cluster to the remoteCluster config</i> added</li></ul> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=783612019-10-15T21:01:01ZPeter Amstutzpeter.amstutz@curii.com
<ul></ul><p>I was going to address <a class="issue tracker-1 status-3 priority-4 priority-default closed" title="Bug: [Workbench2] Automatically add local cluster to the remoteCluster config (Resolved)" href="https://dev.arvados.org/issues/15709">#15709</a> on this branch. I looked at it, remoteHosts already adds the local cluster entry (whether it shows up in the cluster RemoteHosts config or not). I did notice that remoteHostConfigs did not include the local config, and so I added that.</p>
<p>I think this is ready to be looked at.</p> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=784032019-10-16T17:58:47ZEric Biagiotti
<ul></ul><p>Peter Amstutz wrote:</p>
<blockquote>
<p>I was going to address <a class="issue tracker-1 status-3 priority-4 priority-default closed" title="Bug: [Workbench2] Automatically add local cluster to the remoteCluster config (Resolved)" href="https://dev.arvados.org/issues/15709">#15709</a> on this branch. I looked at it, remoteHosts already adds the local cluster entry (whether it shows up in the cluster RemoteHosts config or not). I did notice that remoteHostConfigs did not include the local config, and so I added that.</p>
<p>I think this is ready to be looked at.</p>
</blockquote>
<ul>
<li>Looks like you have to update some of the tests.</li>
</ul>
<ul>
<li>Logging into a cluster that isn't the LoginCluster presents the user with a button that says "Login to X with user from Y". This may be confusing for users in a federation with LoginCluster set. I think its worth conditionally changing that text to just say "Login to X" if there is a LoginCluster.</li>
</ul>
<ul>
<li>The Site-Manager link in search results needs some explanation. Maybe something like: "To manage clusters that are searched see the Site Manager", where instead of a Link, its a Button styled like the others. A right align might work to separate it from the rest of the text on that line also.</li>
</ul>
<ul>
<li>Unfortunately, I think this breaks account linking. When trying to link an account on a non-LoginCluster, it thinks every user is a remote user (uuid points to LoginCluster) and expects you to link to a local account, which wont exist if users are migrated. You probably just have to change link-account-panel-actions.tsx line 205 to compare the uuid against the LoginCuster if it exists.</li>
</ul>
<ul>
<li>Nit: site-manager-panel-root.tsx ln 164: </Typography> needs a tab.</li>
</ul> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=785232019-10-23T14:49:46ZPeter Amstutzpeter.amstutz@curii.com
<ul><li><strong>Target version</strong> changed from <i>2019-10-23 Sprint</i> to <i>2019-11-06 Sprint</i></li></ul> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=785622019-10-24T14:32:12ZPeter Amstutzpeter.amstutz@curii.com
<ul></ul><p>Eric Biagiotti wrote:</p>
<blockquote>
<p>Peter Amstutz wrote:</p>
<blockquote>
<p>I was going to address <a class="issue tracker-1 status-3 priority-4 priority-default closed" title="Bug: [Workbench2] Automatically add local cluster to the remoteCluster config (Resolved)" href="https://dev.arvados.org/issues/15709">#15709</a> on this branch. I looked at it, remoteHosts already adds the local cluster entry (whether it shows up in the cluster RemoteHosts config or not). I did notice that remoteHostConfigs did not include the local config, and so I added that.</p>
<p>I think this is ready to be looked at.</p>
</blockquote>
<ul>
<li>Looks like you have to update some of the tests.</li>
</ul>
</blockquote>
<p>Fixed.</p>
<blockquote>
<ul>
<li>Logging into a cluster that isn't the LoginCluster presents the user with a button that says "Login to X with user from Y". This may be confusing for users in a federation with LoginCluster set. I think its worth conditionally changing that text to just say "Login to X" if there is a LoginCluster.</li>
</ul>
</blockquote>
<p>Now it just says "Log in" when there are not any options. The cluster id is still visible in the upper left.</p>
<blockquote>
<ul>
<li>The Site-Manager link in search results needs some explanation. Maybe something like: "To manage clusters that are searched see the Site Manager", where instead of a Link, its a Button styled like the others. A right align might work to separate it from the rest of the text on that line also.</li>
</ul>
</blockquote>
<p>Tweaked it a little bit. It's hard to make it a button and also explain why it is there, so it is just a link.</p>
<blockquote>
<ul>
<li>Unfortunately, I think this breaks account linking. When trying to link an account on a non-LoginCluster, it thinks every user is a remote user (uuid points to LoginCluster) and expects you to link to a local account, which wont exist if users are migrated. You probably just have to change link-account-panel-actions.tsx line 205 to compare the uuid against the LoginCuster if it exists.</li>
</ul>
</blockquote>
<p>Now disables account linking entirely unless you're on the home cluster.</p>
<blockquote>
<ul>
<li>Nit: site-manager-panel-root.tsx ln 164: </Typography> needs a tab.</li>
</ul>
</blockquote>
<p>Fixed.</p>
<p>15530-wb2-logincluster @ <a class="changeset" title="15530: Fix tests" href="https://dev.arvados.org/projects/arvados/repository/arvados/revisions/df4133dde10614e53a41b16a5c6062c3d1777059">df4133dde10614e53a41b16a5c6062c3d1777059</a></p> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=785932019-10-24T23:38:07ZEric Biagiotti
<ul></ul><ul>
<li>On a remote clusters link account page, users don't know what the login cluster is, so its not worth mentioning especially since we give them a link anyway. I would change the text to "Account linking is unavailable on this cluster. You must visit zzzzz to link accounts." Or something like that.</li>
</ul>
<ul>
<li>On the search results page, if there is only 1 cluster, I would take out the whole heading saying what cluster is being searched and the link to site manager. At the very least, make "clusters" singular.</li>
</ul>
<ul>
<li>Whitespace issues in link-account-panel-root.tsx and site-manager-panel-root.tsx.</li>
</ul> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=786092019-10-25T19:31:29ZPeter Amstutzpeter.amstutz@curii.com
<ul></ul><p>Eric Biagiotti wrote:</p>
<blockquote>
<ul>
<li>On a remote clusters link account page, users don't know what the login cluster is, so its not worth mentioning especially since we give them a link anyway. I would change the text to "Account linking is unavailable on this cluster. You must visit zzzzz to link accounts." Or something like that.</li>
</ul>
</blockquote>
<p>Now it says "Please visit cluster xxxxx to perform account linking"</p>
<blockquote>
<ul>
<li>On the search results page, if there is only 1 cluster, I would take out the whole heading saying what cluster is being searched and the link to site manager. At the very least, make "clusters" singular.</li>
</ul>
</blockquote>
<p>I reworked this (and ended up tinkering with the rendering some more).</p>
<blockquote>
<ul>
<li>Whitespace issues in link-account-panel-root.tsx and site-manager-panel-root.tsx.</li>
</ul>
</blockquote>
<p>Fixed? I think? Relying on auto-indent from the language server.</p> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=786152019-10-25T21:39:22ZEric Biagiotti
<ul></ul><p>Peter Amstutz wrote:</p>
<blockquote>
<p>Eric Biagiotti wrote:</p>
<blockquote>
<ul>
<li>On a remote clusters link account page, users don't know what the login cluster is, so its not worth mentioning especially since we give them a link anyway. I would change the text to "Account linking is unavailable on this cluster. You must visit zzzzz to link accounts." Or something like that.</li>
</ul>
</blockquote>
<p>Now it says "Please visit cluster xxxxx to perform account linking"</p>
<blockquote>
<ul>
<li>On the search results page, if there is only 1 cluster, I would take out the whole heading saying what cluster is being searched and the link to site manager. At the very least, make "clusters" singular.</li>
</ul>
</blockquote>
<p>I reworked this (and ended up tinkering with the rendering some more).</p>
<blockquote>
<ul>
<li>Whitespace issues in link-account-panel-root.tsx and site-manager-panel-root.tsx.</li>
</ul>
</blockquote>
<p>Fixed? I think? Relying on auto-indent from the language server.</p>
</blockquote>
<p>This LGTM. I won't hold up the merge if you think link-account-panel-root.tsx is OK the way it is (I don't). Going forward, if the language server is mangling code, please don't commit it. It obscured your actual changes and made review more difficult.</p> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=786172019-10-28T14:19:12ZPeter Amstutzpeter.amstutz@curii.com
<ul></ul><p>Eric Biagiotti wrote:</p>
<blockquote>
<p>This LGTM. I won't hold up the merge if you think link-account-panel-root.tsx is OK the way it is (I don't).</p>
</blockquote>
<p>This comment is vague. Are you referring to the code formatting or something functional?</p>
<blockquote>
<p>Going forward, if the language server is mangling code, please don't commit it. It obscured your actual changes and made review more difficult.</p>
</blockquote>
<p>Well the review comment was non-specific "whitespace issues". So maybe I should have just left it alone rather than bulk reformat it. Unfortunately the language server I'm using has different ideas about how things should be indented than the original developers, perhaps we need to harmonize on a code formatter or particular settings.</p> Arvados - Feature #15530: Workbench2 trusts federation usershttps://dev.arvados.org/issues/15530?journal_id=786272019-10-28T16:02:06ZPeter Amstutzpeter.amstutz@curii.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li></ul>