Key Pair Authentication
An identity authentication mechanism based on RSA public-key cryptography: the client holds a private key, the server registers the public key, and identity is confirmed through signing and signature verification, without transmitting passwords or sharing secret keys.
Timeline (last 90 days)
The four supporting designs that turn "writing directly into the customer's Snowflake" from a concept into an operable solution are: key-pair auth, a fixed schema, grants up front, and a freshness check.
Snowflake's key-pair authentication is based on the RSA public-key encryption system: the client generates a key pair and registers the public key on the Snowflake user, while the private key is kept by the client; when connecting, the client signs a JWT with the private key, and Snowflake verifies the signature with the public key to confirm identity, with no password or shared secret transmitted throughout the process.
All Facts (2)
The four supporting designs that turn "writing directly into the customer's Snowflake" from a concept into an operable solution are: key-pair auth, a fixed schema, grants up front, and a freshness check.
50%UnverifiedSnowflake's key-pair authentication is based on the RSA public-key encryption system: the client generates a key pair and registers the public key on the Snowflake user, while the private key is kept by the client; when connecting, the client signs a JWT with the private key, and Snowflake verifies the signature with the public key to confirm identity, with no password or shared secret transmitted throughout the process.
50%