{% hint style="warning" %} This page applies to Feast 0.7. The content may be out of date for Feast 0.8+ {% endhint %}

Feast supports the following security methods:

• SSL/TLS on messaging between Feast Core, Feast Online Serving and Feast SDKs.
• Authentication to Feast Core and Serving based on Open ID Connect ID tokens.
• Authorization based on project membership and delegating authorization grants to external Authorization Server.

Important considerations when integrating Authentication/Authorization.

Feast supports SSL/TLS encrypted inter-service communication among Feast Core, Feast Online Serving, and Feast SDKs.

The following properties configure SSL/TLS. These properties are located in their corresponding application.ymlfiles:

Read more on enabling SSL/TLS in the gRPC starter docs.

To enable SSL/TLS in the Feast Python SDK or Feast CLI, set the config options via feast config:

{% hint style="info" %} The Python SDK automatically uses SSL/TLS when connecting to Feast Core and Feast Online Serving via port 443. {% endhint %}

Configure SSL/TLS on the Go SDK by passing configuration via SecurityConfig:

cli, err := feast.NewSecureGrpcClient("localhost", 6566, feast.SecurityConfig{
    EnableTLS: true,
 		TLSCertPath: "/path/to/cert.pem",
})Option

Configure SSL/TLS on the Feast Java SDK by passing configuration via SecurityConfig:

FeastClient client = FeastClient.createSecure("localhost", 6566, 
    SecurityConfig.newBuilder()
      .setTLSEnabled(true)
      .setCertificatePath(Optional.of("/path/to/cert.pem"))
      .build());

{% hint style="warning" %} To prevent man in the middle attacks, we recommend that SSL/TLS be implemented prior to authentication. {% endhint %}

Authentication can be implemented to identify and validate client requests to Feast Core and Feast Online Serving. Currently, Feast uses Open ID Connect (OIDC) ID tokens (i.e. Google Open ID Connect) to authenticate client requests.

Authentication can be configured for Feast Core and Feast Online Serving via properties in their corresponding application.yml files:

{% hint style="info" %} jwkEndpointURIis set to retrieve Google's OIDC JWK by default, allowing OIDC ID tokens issued by Google to be used for authentication. {% endhint %}

Behind the scenes, Feast Core and Feast Online Serving authenticate by:

• Extracting the OIDC ID token TOKENfrom gRPC metadata submitted with request:

('authorization', 'Bearer: TOKEN')

• Validates token's authenticity using the JWK retrieved from the jwkEndpointURI

Feast Online Serving communicates with Feast Core during normal operation. When both authentication and authorization are enabled on Feast Core, Feast Online Serving is forced to authenticate its requests to Feast Core. Otherwise, Feast Online Serving produces an Authentication failure error when connecting to Feast Core.

Properties used to configure Serving authentication via application.yml:

{% tabs %} {% tab title="Google Provider" %} Google Provider automatically extracts the credential from the credential JSON file.

• Set GOOGLE_APPLICATION_CREDENTIALS environment variable to the path of the credential in the JSON file. {% endtab %}

{% tab title="OAuth Provider" %} OAuth Provider makes an OAuth client credentials request to obtain the credential. OAuth requires the following options to be set at feast.security.core-authentication.options.:

Configure the Feast Python SDK and Feast CLI to use authentication via feast config:

$ feast config set enable_auth true

{% tabs %} {% tab title="Google Provider" %} Google Provider automatically finds and uses Google Credentials to authenticate requests:

• Google Provider automatically uses established credentials for authenticating requests if you are already authenticated with the gcloud CLI via:

$ gcloud auth application-default login

• Alternatively Google Provider can be configured to use the credentials in the JSON file viaGOOGLE_APPLICATION_CREDENTIALS environmental variable (Google Cloud Authentication documentation):

$ export GOOGLE_APPLICATION_CREDENTIALS="path/to/key.json"

{% endtab %}

{% tab title="OAuth Provider" %} OAuth Provider makes an OAuth client credentials request to obtain the credential/token used to authenticate Feast requests. The OAuth provider requires the following config options to be set via feast config:

Configure the Feast Java SDK to use authentication by specifying the credential via SecurityConfig:

// error handling omitted.
// Use Google Credential as provider.
cred, _ := feast.NewGoogleCredential("localhost:6566")
cli, _ := feast.NewSecureGrpcClient("localhost", 6566, feast.SecurityConfig{
  // Specify the credential to provide tokens for Feast Authentication.  
	Credential: cred, 
})

{% tabs %} {% tab title="Google Credential" %} Google Credential uses Service Account credentials JSON file set viaGOOGLE_APPLICATION_CREDENTIALS environmental variable (Google Cloud Authentication documentation) to obtain tokens for Authenticating Feast requests:

• Exporting GOOGLE_APPLICATION_CREDENTIALS

$ export GOOGLE_APPLICATION_CREDENTIALS="path/to/key.json"

• Create a Google Credential with target audience.

cred, _ := feast.NewGoogleCredential("localhost:6566")

Target audience of the credential should be set to host URL of target Service. (ie https://localhost if Service listens on localhost): {% endtab %}

{% tab title="OAuth Credential" %} OAuth Credential makes an OAuth client credentials request to obtain the credential/token used to authenticate Feast requests:

• Create OAuth Credential with parameters:

cred := feast.NewOAuthCredential("localhost:6566", "client_id", "secret", "https://oauth.endpoint/auth")

Configure the Feast Java SDK to use authentication by setting credentials via SecurityConfig:

// Use GoogleAuthCredential as provider.
CallCredentials credentials = new GoogleAuthCredentials(
    Map.of("audience", "localhost:6566"));

FeastClient client = FeastClient.createSecure("localhost", 6566, 
    SecurityConfig.newBuilder()
      // Specify the credentials to provide tokens for Feast Authentication.  
      .setCredentials(Optional.of(creds))
      .build());

{% tabs %} {% tab title="GoogleAuthCredentials" %} GoogleAuthCredentials uses Service Account credentials JSON file set viaGOOGLE_APPLICATION_CREDENTIALS environmental variable (Google Cloud authentication documentation) to obtain tokens for Authenticating Feast requests:

• Exporting GOOGLE_APPLICATION_CREDENTIALS

$ export GOOGLE_APPLICATION_CREDENTIALS="path/to/key.json"

• Create a Google Credential with target audience.

CallCredentials credentials = new GoogleAuthCredentials(
    Map.of("audience", "localhost:6566"));

Target audience of the credentials should be set to host URL of target Service. (ie https://localhost if Service listens on localhost): {% endtab %}

{% tab title="OAuthCredentials" %} OAuthCredentials makes an OAuth client credentials request to obtain the credential/token used to authenticate Feast requests:

• Create OAuthCredentials with parameters:

CallCredentials credentials = new OAuthCredentials(Map.of(
  "audience": "localhost:6566",
  "grant_type", "client_credentials",
  "client_id", "some_id",
  "client_id", "secret",
  "oauth_url", "https://oauth.endpoint/auth",
  "jwkEndpointURI", "https://jwk.endpoint/jwk"));

{% hint style="info" %} Authorization requires that authentication be configured to obtain a user identity for use in authorizing requests. {% endhint %}

Authorization provides access control to FeatureTables and/or Features based on project membership. Users who are members of a project are authorized to:

• Create and/or Update a Feature Table in the Project.
• Retrieve Feature Values for Features in that Project.

Feast delegates Authorization grants to an external Authorization Server that implements the Authorization Open API specification.

• Feast checks whether a user is authorized to make a request by making a checkAccessRequest to the Authorization Server.
• The Authorization Server should return a AuthorizationResult with whether the user is allowed to make the request.

Authorization can be configured for Feast Core and Feast Online Serving via properties in their corresponding application.yml

{% hint style="info" %} This example of the Authorization Server with Keto can be used as a reference implementation for implementing an Authorization Server that Feast supports. {% endhint %}

When using Authentication & Authorization, consider:

• Enabling Authentication without Authorization makes authentication optional. You can still send unauthenticated requests.
• Enabling Authorization forces all requests to be authenticated. Requests that are not authenticated are dropped.