Questo contenuto non è disponibile nella lingua selezionata.
Chapter 3. REST API authentication configurations
Use REST API authentication configurations to secure programmatic interactions with the OpenShift Lightspeed Service.
You must configure the appropriate authentication modules and follow security guidelines to manage service access in production and development environments.
3.1. REST API authentication configurations Copia collegamentoCollegamento copiato negli appunti!
Configure REST API authentication for OpenShift Lightspeed by using the authentication_config.module parameter. Selecting the correct module ensures authorized access and maintains environment security.
The OpenShift Lightspeed REST API requires authentication by default. You can define the authentication behavior by using the authentication_config.module parameter in your YAML configuration file.
The following modules are supported for the authentication_config.module parameter:
k8s-
The default authentication module. This module uses Kubernetes
TokenReviewandSubjectAccessReviewto validate authentication. noop- Disables cluster validation and provides no-operation authentication. This logs insecure-mode warnings at startup.
noop-with-token-
Disables cluster validation but still requires a Bearer token in the
Authorizationheader.
Setting the authentication module to noop or setting dev_config.disable_auth to true bypasses all access control. Do not use these settings in a production environment.