Age | Commit message (Collapse) | Author | Files | Lines |
|
As part of the ServiceMesh solution OAuth2-proxy will be used
to enable a central authentication and authorization for ONAP
Service Access.
This patch delivers the function based on oauth2-proxy helmcharts:
https://github.com/oauth2-proxy/manifests/tree/main/helm/oauth2-proxy
Issue-ID: OOM-2489
Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
Change-Id: Iafa82813a7b9494cf13d77d47a39fc6030cb919b
|
|
Add the oauth2-proxy client to the ONAP keycloak REALM
Issue-ID: OOM-2489
Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
Change-Id: I3c38df8ad79a7cdaa87f4b55b1bb38afb18d2c0e
|
|
As part of the ServiceMesh solution Keycloak will be used
to enable a central authentication and authorization for ONAP
Service Access. This chart provides the import of a default
ONAP Realm to an existing Keycloak Instance (alternative
to a combined KC+REALM installation).
It contains clients for the planned portal-ng.
Make all subcomponents selectable
Issue-ID: OOM-3021
Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
Change-Id: I677a3b9e200299c2cde7774e09db6cf33ac510b7
|