view.html.erb

<%-
  # /rnode/ is the relative-path proxy: it strips the /rnode/HOST/PORT prefix
  # before forwarding to the backend, so the interLink API paths are preserved.
  # /node/ sends the full path (including prefix) to the backend.
  rnode_base_url = "/rnode/#{host}/#{port}"
  node_base_url  = "/node/#{host}/#{port}"
-%>

<div class="alert alert-success" role="alert">
  InterLink services are running.
</div>

<ul>
  <li><strong>InterLink server:</strong> <code><%= host %>:<%= port %></code></li>
  <li><strong>InterLink plugin socket:</strong> <code><%= interlink_plugin_socket %></code></li>
  <li>
    <strong>Server URL through OnDemand (recommended):</strong>
    <code><%= rnode_base_url %></code>
    <small class="text-muted"> — use <code>/rnode/</code> so API paths are forwarded correctly</small>
  </li>
  <li><strong>Server config:</strong> <code><%= interlink_server_config %></code></li>
  <li><strong>Plugin config:</strong> <code><%= interlink_plugin_config %></code></li>
</ul>

<div class="alert alert-info" role="alert">
  <strong>Authentication for programmatic API clients (e.g. interlink-vk):</strong>
  <p>
    OOD sets the <code>X-Forwarded-User</code> header to the authenticated username
    on every proxied request. Configure interLink to authorise based on this header —
    no separate bearer token is needed from the client.
  </p>
  <p>
    See <a href="https://github.com/OSC/ondemand/issues/5514" target="_blank">OSC/ondemand#5514</a>
    for full technical details.
  </p>
</div>

<p>
  Configure your interlink-vk pod to reach the InterLink server at
  <code><%= rnode_base_url %></code> and set <code>rnode_uri: '/rnode'</code>
  in your site's <code>ood_portal.yml</code>.
</p>