Bug #15867
Updated by Peter Amstutz over 4 years ago
The login redirect generated by Controller passes an empty "remote" which causes the target cluster to fail:
<pre>
https://172.17.0.2:8000/login?remote=&return_to=https%3A%2F%2F172.17.0.3%2Fusers%2Fwelcome%3Freturn_to%3D%252F
</pre>
<pre>
{"errors":["Invalid remote cluster id (req-1dbjeioi2ubya1rjphw3)"],"error_token":"1574438263+155fa05c"}
</pre>
Either controller shouldn't do that, or the API server should accept that (or both).