This topic describes authentication information for Assured Workloads.
Supported authentication methods
Assured Workloads supports the following authentication methods.
Service accounts are recommended for almost all use cases, whether you are developing locally or in a production application. For an example of how to set up authentication with a service account, see Assured Workloads client libraries.
For more information about setting up authentication with a production application, see Setting up authentication for server to server production applications.
You can authenticate users directly to your application, when the application needs to access resources on behalf of an end user. For most use cases, we recommend using a service account instead.
Examples of why to use user accounts with Assured Workloads include:
If your application uses end user authentication, you need to specify OAuth scopes when making a method call. For more information about the OAuth scopes that you need in order to call a method, see the relevant method in the Assured Workloads reference.
For more information about setting up authentication with user accounts, see Authenticating as an end user.
When an application calls a Google Cloud API, IAM checks that the caller has an identity with the permissions required to use the resource.
For example, user and service accounts are identities. To make permissions available to a user or service account, grant it at least one IAM role. A role contains a set of permissions that allows you to perform specific actions on Google Cloud resources.
For more information about the roles for Assured Workloads, see Assured Workloads access control.
- Learn more about Google Cloud authentication.