Azure Load Balancer with Ignition Cloud Edition and IDP

Ignition
,
1

Reaching out to the forum to see if anyone has experience with configuring an Azure Load Balancer with Ignition Cloud Edition and IDP. I have reviewed the AWS Ignition KB (Application Load Balancers and Ignition), but there are (from what I can tell) some differences in the Azure environment.

The pseudo process I am hoping for is:

  1. Client goes to URL --> Load Balancer (End point somewhere.com)
  2. Load Balance (LB) --> IDP (LB redirects Client to IDP for authentication)
  3. IDP --> LB (IDP authenticates user and pass token to LB)
  4. LB --> Ignition Gateway (Load balancer pass user token to Gateway with a 'sticky' session connection.)
  5. Ignition Gateway (IGW) --> LB --> Client (Perspective page received by user)

Any experience out there that I can draw upon?

2

I think you'll want to actually configure Ignition with an [Identity Provider}(Configuring Identity Providers | Ignition User Manual) configuration instead of having the Azure LB inject the auth. A few reasons why include:

  • With the proposed configuration, you won't be able to launch the Designer (it doesn't yet tolerate that kind of injected auth flow) against the gateway. You'd need a separate path.
  • While you could use this method to "gate" access to a Perspective app, you won't be able to leverage any Ignition security features, as the user won't be logged into the app itself.