@@ -356,10 +356,10 @@ const service = ExampleServiceV1.newInstance(options);
356
356
## Container Authentication
357
357
The ` ContainerAuthenticator ` is intended to be used by application code
358
358
running inside a compute resource managed by the IBM Kubernetes Service (IKS)
359
- in which a secure compute resource token (CR token) has been stored in a file
360
- within the compute resource's local file system.
359
+ or IBM Cloud Code Engine in which a secure compute resource token (CR token)
360
+ has been stored in a file within the compute resource's local file system.
361
361
The CR token is similar to an IAM apikey except that it is managed automatically by
362
- the compute resource provider (IKS).
362
+ the compute resource provider (IKS or Code Engine ).
363
363
This allows the application developer to:
364
364
- avoid storing credentials in application code, configuration files or a password vault
365
365
- avoid managing or rotating credentials
@@ -379,7 +379,9 @@ The IAM access token is added to each outbound request in the `Authorization` he
379
379
380
380
- crTokenFilename: (optional) the name of the file containing the injected CR token value.
381
381
If not specified, then the authenticator will first try ` /var/run/secrets/tokens/vault-token `
382
- and then ` /var/run/secrets/tokens/sa-token ` as the default value (first file found is used).
382
+ and then ` /var/run/secrets/tokens/sa-token ` and finally
383
+ ` /var/run/secrets/codeengine.cloud.ibm.com/compute-resource-token/token ` as the default value
384
+ (first file found is used).
383
385
The application must have ` read ` permissions on the file containing the CR token value.
384
386
385
387
- iamProfileName: (optional) the name of the linked trusted IAM profile to be used when obtaining the
0 commit comments