You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: rest-api/cli/README.md
+11-3Lines changed: 11 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -174,6 +174,7 @@ The scalar fields listed below can also be set via a `NICO_*` environment variab
174
174
|`NICO_TOKEN_COMMAND`|`auth.token_command`| Shell command that prints a bearer token |
175
175
|`NICO_AUTH_SCRIPT`|`auth.token_command`| Alias of `NICO_TOKEN_COMMAND` (canonical name wins when both set) |
176
176
|`NICO_TOKEN_URL`|`auth.oidc.token_url`||
177
+
|`NICO_KEYCLOAK_REALM`|`auth.oidc.realm`| Used only when the token endpoint is built from `--keycloak-url`|
177
178
|`NICO_CLIENT_ID`|`auth.oidc.client_id`||
178
179
|`NICO_CLIENT_SECRET`|`auth.oidc.client_secret`||
179
180
|`NICO_OIDC_USERNAME`|`auth.oidc.username`||
@@ -185,7 +186,14 @@ The scalar fields listed below can also be set via a `NICO_*` environment variab
185
186
|`NICO_AUTHN_URL`|`auth.api_key.authn_url`| Required for legacy NGC keys; ignored for `nvapi-` bearer keys |
186
187
|`NICO_API_KEY_TOKEN`|`auth.api_key.token`| Persisted token after NGC exchange |
187
188
188
-
`NICO_KEYCLOAK_URL` and `NICO_KEYCLOAK_REALM` do not map to a single config field; they feed the login command and construct the OIDC `token_url` at login time.
189
+
`NICO_KEYCLOAK_URL` does not map to a config field of its own; it feeds the login command and
190
+
constructs the OIDC `token_url`, which is what gets persisted.
191
+
192
+
`--keycloak-realm` and `--client-id` both carry built-in defaults (`nico-dev` and `nico-api`)
193
+
that match the Kustomize development realm, not the realm `helm-prereqs/setup.sh` installs.
194
+
Set `auth.oidc.realm` and `auth.oidc.client_id` for your deployment rather than relying on
195
+
them. When a login fails, the error names the token endpoint it contacted and any value that
196
+
came from a built-in default.
189
197
190
198
Client-credentials configurations can also set `auth.oidc.scopes` as a YAML list,
191
199
`auth.oidc.token_parameters` as a map of additional non-secret form parameters,
0 commit comments