Section 3.3 has the student set a custom egress route to allow polling of configs from remote system-provider API Manager.
Interestingly, an authrep GET request to the backend-listener of API Manager also becomes accessible even though the egress route is specific to the system-provider.
Would be interesting to better understand why access to the backend-listener is allowed.
Its not a show-stopper for the lab.
Chances are students won't even notice this is occurring.
Section 3.3 has the student set a custom egress route to allow polling of configs from remote system-provider API Manager. Interestingly, an authrep GET request to the backend-listener of API Manager also becomes accessible even though the egress route is specific to the system-provider.
Would be interesting to better understand why access to the backend-listener is allowed. Its not a show-stopper for the lab.
Chances are students won't even notice this is occurring.