You can deploy SAML in scenarios where multiple Service Providers process SAML requests forwarded by a reverse-proxy or a load balancer.
In order to configure SAML for deployment, set the values for the below properties by creating an environment variable for each property.
...
...
...
In Adeptia Connect, the request is always forwarded via webapp-gateway microservice. You can also use an additional load balancer (Ingress) to receive an incoming request first and then send it to the webapp-gateway.
For enabling SAML SSO in Adeptia Connect, you need to set the values for the following environment variables based on whether you are using webapp-gateway or an Ingress to communicate with the portal microservice. You can find these environment variables in the portal section of the global values.yaml file.
| Info |
|---|
| The values for these environment variables will change in case you're using only the webapp-gateway microservice to communicate with the portal microservice. |
| Variable Name | Example value | Description |
|---|---|---|
SAML_SSO_CONTEXT_PROVIDER_LB_CONTEXT_PATH | / | Prefix of a URL path used to select the context(s) to which an incoming request is passed. A URL is in the format: http://hostname.com/contextPath/, where each of the path elements can be zero or more separated elements. It must be /. |
...
...
SAML_SSO_CONTEXT_PROVIDER_LB_INCLUDE_SERVER_PORT_IN_REQUEST_URL | true | To include server port number in the URL or not. |
SAML_SSO_CONTEXT_PROVIDER_LB_SCHEME | http | Name of the scheme (http or https). |
SAML_SSO_CONTEXT_PROVIDER_LB_SERVER_NAME | localhost | Name of the server. |
SAML_SSO_CONTEXT_PROVIDER_LB_SERVER_PORT | 9090 |
...
| borderStyle | solid |
|---|---|
| title | You may be interested in... |
...
Port number of the server. |