Since login-gateway will be deployed separately, the services using it will not be "behind the gateway" automatically (it does not relay request to services, besides obtaining the JWT initially, in any way). The servies will need to validate the JWT coming in in headers to allow users to operate.
While this can be done in a general fashion (for all kinds of JWT-compatible environments with just vanilla JWT libraries) based on hopefully completly detailed information provided in #10, for selected environments that AbsaOSS frequently uses (Springboot @ Scala 2.12/2.13) a convenince library may be beneficial and streamline the integration process.
Hint
Client library does not need to be written from scratch, it's skeleton can be generated from the api doc -- see #14 for hints how to get to the api doc (YAML) and then use the generators (e.g. online https://editor.swagger.io/ or locally)
Since login-gateway will be deployed separately, the services using it will not be "behind the gateway" automatically (it does not relay request to services, besides obtaining the JWT initially, in any way). The servies will need to validate the JWT coming in in headers to allow users to operate.
While this can be done in a general fashion (for all kinds of JWT-compatible environments with just vanilla JWT libraries) based on hopefully completly detailed information provided in #10, for selected environments that AbsaOSS frequently uses (Springboot @ Scala 2.12/2.13) a convenince library may be beneficial and streamline the integration process.
Hint
Client library does not need to be written from scratch, it's skeleton can be generated from the api doc -- see #14 for hints how to get to the api doc (YAML) and then use the generators (e.g. online https://editor.swagger.io/ or locally)