Skip to content

MAS Proxy

Our MAS proxy is an nginx configuration to make it possible to use the MAS Mange Ui inide of the Insight Control Panel, while using it in a browser.

With the switch to MAS, it's not possible to use the newly MAS Manage application inside of an iframe anymore. Various CORS configurations, for MAS Mange but also the authentication process, get in the way. To work around that we provide a proxy that be run alongside Insight.

It handles various parts of the Manage web interface, including headers and cookies, and makes it possible to access the Manage application through a different hostname. The procude is documented by IBM here

Our configuration only allows access to the following hostnames:

  • .manage.some.mas.domain.tld
  • api.some.mas.domain.tld
  • auth.some.mas.domain.tld

Requirements

  • required DNS entries must point to your Ingress controller or HTTP proxy
  • valid certificate(s) for all required hostnames

Configuration

Image: rodias.azurecr.io/mas-proxy:latest

ENV Description
MAS_DOMAIN the basic domain/hostname of the MAS environment, some.mas.domain.tld from the example
MAS_INSTANCE the instance name of your manage application
PROXY_DOMAIN the basic domain/hostname of your Insight environment

Client Configuration

When the MAS-proxy is running configure the client to use it by configuring:

{
  "maximoUi": "https://<instance>.manage.some.mas.domain.tld/maximo",
}