@@ -336,10 +336,10 @@ ExampleService service = ExampleService.newInstance("example_service");
336336## Container Authentication
337337The ` ContainerAuthenticator ` is intended to be used by application code
338338running inside a compute resource managed by the IBM Kubernetes Service (IKS)
339- in which a secure compute resource token (CR token) has been stored in a file
340- within the compute resource's local file system.
339+ or IBM Cloud Code Engine in which a secure compute resource token (CR token)
340+ has been stored in a file within the compute resource's local file system.
341341The CR token is similar to an IAM apikey except that it is managed automatically by
342- the compute resource provider (IKS).
342+ the compute resource provider (IKS or Code Engine ).
343343This allows the application developer to:
344344- avoid storing credentials in application code, configuration files or a password vault
345345- avoid managing or rotating credentials
@@ -359,7 +359,9 @@ The IAM access token is added to each outbound request in the `Authorization` he
359359
360360- crTokenFilename: (optional) the name of the file containing the injected CR token value.
361361If not specified, then the authenticator will first try ` /var/run/secrets/tokens/vault-token `
362- and then ` /var/run/secrets/tokens/sa-token ` as the default value (first file found is used).
362+ and then ` /var/run/secrets/tokens/sa-token ` and finally
363+ ` /var/run/secrets/codeengine.cloud.ibm.com/compute-resource-token/token ` as the default value
364+ (first file found is used).
363365The application must have ` read ` permissions on the file containing the CR token value.
364366
365367- iamProfileName: (optional) the name of the linked trusted IAM profile to be used when obtaining the
0 commit comments