CREATE SECRET¶

Creates a new secret in the current or specified schema or replaces an existing secret.

See also:: ALTER SECRET , DESCRIBE SECRET , DROP SECRET , SHOW SECRETS

Syntax¶

OAuth with client credentials flow:

CREATE [ OR REPLACE ] SECRET [ IF NOT EXISTS ] <name>
  TYPE = OAUTH2
  API_AUTHENTICATION = <security_integration_name>
  OAUTH_SCOPES = ( '<scope_1>' [ , '<scope_2>' ... ] )
  [ COMMENT = '<string_literal>' ]

Copy

OAuth with authorization code grant flow:

CREATE [ OR REPLACE ] SECRET [ IF NOT EXISTS ] <name>
  TYPE = OAUTH2
  OAUTH_REFRESH_TOKEN = '<string_literal>'
  OAUTH_REFRESH_TOKEN_EXPIRY_TIME = '<string_literal>'
  API_AUTHENTICATION = <security_integration_name>;
  [ COMMENT = '<string_literal>' ]

Copy

Cloud provider:

CREATE [ OR REPLACE ] SECRET [ IF NOT EXISTS ] <name>
  TYPE = CLOUD_PROVIDER_TOKEN
  API_AUTHENTICATION = '<cloud_provider_security_integration>'
  ENABLED = { TRUE | FALSE }
  [ COMMENT = '<string_literal>' ]

Copy

Basic authentication:

CREATE [ OR REPLACE ] SECRET [ IF NOT EXISTS ] <name>
  TYPE = PASSWORD
  USERNAME = '<username>'
  PASSWORD = '<password>'
  [ COMMENT = '<string_literal>' ]

Copy

Generic string:

CREATE [ OR REPLACE ] SECRET [ IF NOT EXISTS ] <name>
  TYPE = GENERIC_STRING
  SECRET_STRING = '<string_literal>'
  [ COMMENT = '<string_literal>' ]

Copy

Symmetric key:

CREATE [ OR REPLACE ] SECRET [ IF NOT EXISTS ] <name>
TYPE = SYMMETRIC_KEY
ALGORITHM = GENERIC

Copy

OAuth with client credentials flow required parameters¶

name

String that specifies the identifier (i.e. name) for the secret, must be unique in your schema.

In addition, the identifier must start with an alphabetic character and cannot contain spaces or special characters unless the entire identifier string is enclosed in double quotes (e.g. "My object"). Identifiers enclosed in double quotes are also case-sensitive.

For more details, see Identifier requirements.

TYPE = OAUTH2

Specifies a secret to use with an OAuth grant flow.

API_AUTHENTICATION = security_integration_name

Specifies the name value of the Snowflake security integration that connects Snowflake to an external service.

OAUTH_SCOPES = ( 'scope_1' [ , 'scope_2' ... ] )

Specifies a comma-separated list of scopes to use when making a request from the OAuth server by a role with USAGE on the integration during the OAuth client credentials flow.

This list must be a subset of the scopes defined in the OAUTH_ALLOWED_SCOPES property of the security integration. If the OAUTH_SCOPES property values are not specified, the secret inherits all of the scopes that are specified in the security integration.

For the ServiceNow connector, the only possible scope value is 'useraccount'.

OAuth with authorization code grant flow required parameters¶

name

String that specifies the identifier (i.e. name) for the secret, must be unique in your schema.

For more details, see Identifier requirements.

TYPE = OAUTH2

Specifies a secret to use with the OAuth grant flow.

OAUTH_REFRESH_TOKEN = 'string_literal'

Specifies the token as a string that is used to obtain a new access token from the OAuth authorization server when the access token expires.

OAUTH_REFRESH_TOKEN_EXPIRY_TIME = 'string_literal'

Specifies the timestamp as a string when the OAuth refresh token expires.

API_AUTHENTICATION = security_integration_name

Specifies the name value of the Snowflake security integration that connects Snowflake to an external service.

AWS IAM required parameters¶

TYPE = CLOUD_PROVIDER_TOKEN: Specifies that this is secret for use with a cloud provider, such as Amazon Web Services (AWS).
API_AUTHENTICATION = 'cloud_provider_security_integration': Specifies the name value of the Snowflake security integration that connects Snowflake to a cloud provider.

Basic authentication required parameters¶

name

String that specifies the identifier (i.e. name) for the secret, must be unique in your schema.

For more details, see Identifier requirements.

TYPE = PASSWORD

Specifies a secret to use with basic authentication.

When specifying this type you must specify values for the username and password properties.

USERNAME = 'username'

Specifies the username value to store in the secret.

Specify this value when setting the TYPE value to PASSWORD for use with basic authentication.

PASSWORD = 'password'

Specifies the password value to store in the secret.

Specify this value when setting the TYPE value to PASSWORD for use with basic authentication.

Generic string parameters¶

name

String that specifies the identifier (i.e. name) for the secret, must be unique in your schema.

For more details, see Identifier requirements.

TYPE = GENERIC_STRING

Specifies a secret to store a sensitive string value.

SECRET_STRING = 'string_literal'

Specifies the string to store in the secret.

The string can be an API token or a string of sensitive value that can be used in the handler code of a UDF or stored procedure. For details, see Creating and using an external access integration.

You should not use this property to store any kind of OAuth token; use one of the other secret types for your OAuth use cases.

Symmetric key parameters¶

Symmetric key secrets generate a cryptographic key that can be used for cryptographic operations. Currently only used to generate synthetic data.

ALGORITHM: Specifies which algorithm to use to generate the symmetric key. The only value supported is GENERIC, which generates a 256-bit key.

Optional parameters¶

COMMENT = 'string_literal'

String (literal) that specifies a comment for the secret.

Default: No value

Access control requirements¶

A role used to execute this operation must have the following privileges at a minimum:

Privilege	Object	Notes
CREATE SECRET	Schema
USAGE	Database or schema

The USAGE privilege on the parent database and schema are required to perform operations on any object in a schema. Note that a role granted any privilege on a schema allows that role to resolve the schema. For example, a role granted CREATE privilege on a schema can create objects on that schema without also having USAGE granted on that schema.

For instructions on creating a custom role with a specified set of privileges, see Creating custom roles.

For general information about roles and privilege grants for performing SQL actions on securable objects, see Overview of Access Control.

Usage notes¶

The OR REPLACE and IF NOT EXISTS clauses are mutually exclusive. They can’t both be used in the same statement.
CREATE OR REPLACE <object> statements are atomic. That is, when an object is replaced, the old object is deleted and the new object is created in a single transaction.

Regarding metadata:

Attention

Customers should ensure that no personal data (other than for a User object), sensitive data, export-controlled data, or other regulated data is entered as metadata when using the Snowflake service. For more information, see Metadata fields in Snowflake.

Examples¶

OAuth with client credentials¶

Create a secret for use with the OAuth client credentials flow:

CREATE OR REPLACE SECRET mysecret
  TYPE = OAUTH2
  API_AUTHENTICATION = mysecurityintegration
  OAUTH_SCOPES = ('useraccount')
  COMMENT = 'secret for the service now connector'

Copy

OAuth with authorization code grant¶

Create a secret for use with the OAuth code grant flow:

CREATE SECRET service_now_creds_oauth_code
  TYPE = OAUTH2
  OAUTH_REFRESH_TOKEN = '34n;vods4nQsdg09wee4qnfvadH'
  OAUTH_REFRESH_TOKEN_EXPIRY_TIME = '2022-01-06 20:00:00'
  API_AUTHENTICATION = sn_oauth;

Copy

AWS IAM¶

Create a secret for use with Amazon Web Services (AWS) by including the AWS IAM ARN for authentication:

CREATE SECRET aws_secret
  TYPE = CLOUD_PROVIDER_TOKEN
  API_AUTHENTICATION = myawsiamintegration
  ENABLED = TRUE;

Copy

Basic authentication¶

Create a secret that specifies a username and password to access ServiceNow:

CREATE SECRET service_now_creds_pw
  TYPE = password
  USERNAME = 'jsmith1'
  PASSWORD = 'W3dr@fg*7B1c4j';

Copy