Lines Matching full:sourced

31 …* [Accessing resources using Executable-sourced credentials](#using-executable-sourced-credentials…
36 …* [Accessing resources using Executable-sourced credentials](#using-executable-sourced-workforce-c…
275 (file-sourced credentials) or from a local server (URL-sourced credentials).
277 **File-sourced credentials**
278 For file-sourced credentials, a background process needs to be continuously refreshing the file
283 To generate a file-sourced OIDC configuration, run the following command:
286 # Generate an OIDC configuration file for file-sourced credentials.
308 **URL-sourced credentials**
309 For URL-sourced credentials, a local server needs to host a GET endpoint to return the OIDC token.
313 To generate a URL-sourced OIDC workload identity configuration, run the following command:
316 # Generate an OIDC configuration file for URL-sourced credentials.
342 #### Using Executable-sourced credentials with OIDC and SAML
344 **Executable-sourced credentials**
345 For executable-sourced credentials, a local executable is used to retrieve the 3rd party token. 
349 To use executable-sourced credentials, the `GOOGLE_EXTERNAL_ACCOUNT_ALLOW_EXECUTABLES`
352 To generate an executable-sourced workload identity configuration, run the following command:
355 # Generate a configuration file for executable-sourced credentials.
466 Given the complexity of using executable-sourced credentials, it is recommended to use
467 the existing supported mechanisms (file-sourced/URL-sourced) for providing 3rd party
527 (file-sourced credentials), from a local server (URL-sourced credentials) or by calling an executab…
528 (executable-sourced credentials).
530 **File-sourced credentials**
531 For file-sourced credentials, a background process needs to be continuously refreshing the file
536 To generate a file-sourced OIDC configuration, run the following command:
539 # Generate an OIDC configuration file for file-sourced credentials.
558 To generate a file-sourced SAML configuration, run the following command:
561 # Generate a SAML configuration file for file-sourced credentials.
578 **URL-sourced credentials**
579 For URL-sourced credentials, a local server needs to host a GET endpoint to return the OIDC token.
583 To generate a URL-sourced OIDC workforce identity configuration, run the following command:
586 # Generate an OIDC configuration file for URL-sourced credentials.
604 To generate a URL-sourced SAML configuration, run the following command:
607 # Generate a SAML configuration file for file-sourced credentials.
650 #### Using Executable-sourced workforce credentials with OIDC and SAML
652 **Executable-sourced credentials**
653 For executable-sourced credentials, a local executable is used to retrieve the 3rd party token.
657 To use executable-sourced credentials, the `GOOGLE_EXTERNAL_ACCOUNT_ALLOW_EXECUTABLES`
660 To generate an executable-sourced workforce identity configuration, run the following command:
663 # Generate a configuration file for executable-sourced credentials.
704 Refer to the [using executable-sourced credentials with Workload Identity Federation](#using-execut…
712 Given the complexity of using executable-sourced credentials, it is recommended to use
713 the existing supported mechanisms (file-sourced/URL-sourced) for providing 3rd party