Versions Compared

Old Version 5

changes.mady.by.user Terry van der Griend

Saved on

compared with

New Version Current

changes.mady.by.user Paul Hoeijenbos

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Starting a flow with the JWT authentication provider is different, instead . Instead of directly loading the Development Dashboard on the Runtime, we will load is it through the Gateway Service.

...

All request flow through the Gateway, the . The Gateway is responsible for managing and storing the User Authentication. In the Diagram you can see that the Runtime still validates the authentication but in this scenario is it not responsible for display or doing anything with the authentication flow itself. For this reason the Runtime now is dependent on the Gateway to send a form of authentication along with the Proxy Request.

...

The Development Dashboard is packaged with the Runtime and this is convenient for starting authenticated flows. The Runtime stores its authentication state in a thing called the HTTP Session. This HTTP Session is applicable to all request requests coming from the same domain and path.

...