- Schema:
SECRETS view¶
This Account Usage view provides the secrets in your account.
Each row in this view corresponds to a different secret.
Columns¶
Column Name |
Data Type |
Description |
---|---|---|
|
NUMBER |
Internal, system-generated identifier for the secret. |
|
VARCHAR |
Name of the secret. |
|
NUMBER |
Internal, system-generated identifier for the schema of the secret. |
|
VARCHAR |
Schema that the secret belongs to. |
|
NUMBER |
Internal, system-generated identifier for the database of the secret. |
|
VARCHAR |
Database that the secret belongs to. |
|
VARCHAR |
Name of the role that owns the secret; NULL if it has been dropped. |
|
VARCHAR(13) |
The type of role that owns the object, for example |
|
VARCHAR |
The type of secret ( |
|
TIMESTAMP_LTZ(6) |
The expiry time of the OAuth access token stored in the secret. |
|
TIMESTAMP_LTZ(6) |
The expiry time of the OAuth refresh token stored in the secret. |
|
VARCHAR |
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. |
|
VARCHAR |
The name of the API Authentication Integration used by this secret for authentication. |
|
VARCHAR |
Comment for the secret. |
|
TIMESTAMP_LTZ(6) |
Date and time when the secret was created. |
|
TIMESTAMP_LTZ(6) |
Date and time when the secret was last altered. |
|
TIMESTAMP_LTZ(6) |
Date and time when the secret was dropped. |
Usage notes¶
Latency for the view may be up to 120 minutes (2 hours).
Sensitive values that the secret stores, such as the values for username, password, and OAuth refresh token, are not reported in this view.