Using Studio to Proxy SES

In many cases you might want to restrict access to SES to most users, but will want to let users of Semaphore Studio access the SIS widgets. This is possible - Studio can itself access the SES server using the internal “Semaphore Inter-Service URL” which is likely to be within the Semaphore network therefore not brokered by any intermdiary firewall.

To do this, add the SIS instance to the Studio interface - use the “Services -> Semantic Integration Service” page to create the service. Set the “Semaphore Inter-Service URL” to the value that is required to access the SIS service from the Studio Server. This probably won’t work from the client browser (if it does, then these intructions aren’t necessary for you). Set the Client URL to anything, it’s not going to work. Using the Test button should show “Service is available via Semaphore Inter-Service URL only”.

Now return to the Studio front page and click on the SIS Widgets button. You will be promted to enter select a model name, but this isn’t what we want to do. We want to take the URL from your browser’s address bar, e.g.

http://localhost:5080/sis/widgets/urn:uuid:afa0c3b0-d1b2-40bf-4f68-305f17a2c455/ui/

and amend it to

http://localhost:5080/ses/urn:uuid:afa0c3b0-d1b2-40bf-4f68-305f17a2c455/

(i.e. change /sis/widgets/ to /ses/ and remove the trailing ui/)

Now return to the SIS configuration page and enter this as the Client URL for the SES instance. The Test will now work fully and you will be able to use the SIS widgets - piggy backing the fact that you are already logged into Studio to enable the access to the SIS functionality.

It is possible to retrieve the sis/widgets URL using the GraphQL interface

{
  semanticIntegrationServices {
    name
    sesPath
  }
}

but the same transformation of the data is required.