EPIC - manage authentication and permissions

[benoitdm-oslandia]

"Security" defines how the system checks authentication and permissions

• [ ] #14
• [ ] #15

[benoitdm-oslandia]

marked this issue as related to #13

[benoitdm-oslandia]

marked this issue as related to #14

[benoitdm-oslandia]

In GitLab by @nrevelant on Jul 20, 2022, 16:28

A priori authentication should be supported by components upstream of the transmission of OGC Feature requests (by front-end components + Keycloak).

I understood that the authentication will be done using a JWT type token transmitted with the incoming request.

If a need for permissions management is identified and confirmed, it should then actually concern the OGC Feature service (including for setting these permissions).

• -> In this case, part of the JWT token should be retrieved once the request has been transmitted to the service, in order to identify the user to begin with.
• -> Attention: This need for management of permissions by the service should be specified. But should not include authentication