KeyGenParameterSpec

Kotlin |Java

class KeyGenParameterSpec : AlgorithmParameterSpec

kotlin.Any
↳	android.security.keystore.KeyGenParameterSpec

AlgorithmParameterSpec for initializing a KeyPairGenerator or a KeyGenerator of the Android Keystore system. The spec determines authorized uses of the key, such as whether user authentication is required for using the key, what operations are authorized (e.g., signing, but not decryption), with what parameters (e.g., only with a particular padding scheme or digest), and the key's validity start and end dates. Key use authorizations expressed in the spec apply only to secret keys and private keys -- public keys can be used for any supported operations.

To generate an asymmetric key pair or a symmetric key, create an instance of this class using the Builder, initialize a KeyPairGenerator or a KeyGenerator of the desired key type (e.g., EC or AES -- see KeyProperties.KEY_ALGORITHM constants) from the AndroidKeyStore provider with the KeyGenParameterSpec instance, and then generate a key or key pair using KeyGenerator.generateKey() or KeyPairGenerator.generateKeyPair().

The generated key pair or key will be returned by the generator and also stored in the Android Keystore under the alias specified in this spec. To obtain the secret or private key from the Android Keystore use KeyStore.getKey(String, null) or KeyStore.getEntry(String, null). To obtain the public key from the Android Keystore use java.security.KeyStore#getCertificate(String) and then Certificate.getPublicKey().

To help obtain algorithm-specific public parameters of key pairs stored in the Android Keystore, generated private keys implement java.security.interfaces.ECKey or java.security.interfaces.RSAKey interfaces whereas public keys implement java.security.interfaces.ECPublicKey or java.security.interfaces.RSAPublicKey interfaces.

For asymmetric key pairs, a X.509 certificate will be also generated and stored in the Android Keystore. This is because the java.security.KeyStore abstraction does not support storing key pairs without a certificate. The subject, serial number, and validity dates of the certificate can be customized in this spec. The certificate may be replaced at a later time by a certificate signed by a Certificate Authority (CA).

NOTE: If attestation is not requested using Builder.setAttestationChallenge(byte[]), generated certificate may be self-signed. If a private key is not authorized to sign the certificate, then the certificate will be created with an invalid signature which will not verify. Such a certificate is still useful because it provides access to the public key. To generate a valid signature for the certificate the key needs to be authorized for all of the following:

KeyProperties.PURPOSE_SIGN,
operation without requiring the user to be authenticated (see Builder.setUserAuthenticationRequired(boolean)),
signing/origination at this moment in time (see Builder.setKeyValidityStart(Date) and Builder.setKeyValidityForOriginationEnd(Date)),
suitable digest,
(RSA keys only) padding scheme KeyProperties.SIGNATURE_PADDING_RSA_PKCS1.

NOTE: The key material of the generated symmetric and private keys is not accessible. The key material of the public keys is accessible.

Instances of this class are immutable.

Known issues

A known bug in Android 6.0 (API Level 23) causes user authentication-related authorizations to be enforced even for public keys. To work around this issue extract the public key material to use outside of Android Keystore. For example:

<code>PublicKey unrestrictedPublicKey =
          KeyFactory.getInstance(publicKey.getAlgorithm()).generatePublic(
                  new X509EncodedKeySpec(publicKey.getEncoded()));
  </code>

Example: NIST P-256 EC key pair for signing/verification using ECDSA

This example illustrates how to generate a NIST P-256 (aka secp256r1 aka prime256v1) EC key pair in the Android KeyStore system under alias key1 where the private key is authorized to be used only for signing using SHA-256, SHA-384, or SHA-512 digest and only if the user has been authenticated within the last five minutes. The use of the public key is unrestricted (See Known Issues).

<code>KeyPairGenerator keyPairGenerator = KeyPairGenerator.getInstance(
          KeyProperties.KEY_ALGORITHM_EC, "AndroidKeyStore");
  keyPairGenerator.initialize(
          new KeyGenParameterSpec.Builder(
                  "key1",
                  KeyProperties.PURPOSE_SIGN)
                  .setAlgorithmParameterSpec(new ECGenParameterSpec("secp256r1"))
                  .setDigests(KeyProperties.DIGEST_SHA256,
                          KeyProperties.DIGEST_SHA384,
                          KeyProperties.DIGEST_SHA512)
                  // Only permit the private key to be used if the user authenticated
                  // within the last five minutes.
                  .setUserAuthenticationRequired(true)
                  .setUserAuthenticationValidityDurationSeconds(5 * 60)
                  .build());
  KeyPair keyPair = keyPairGenerator.generateKeyPair();
  Signature signature = Signature.getInstance("SHA256withECDSA");
  signature.initSign(keyPair.getPrivate());
  ...
 
  // The key pair can also be obtained from the Android Keystore any time as follows:
  KeyStore keyStore = KeyStore.getInstance("AndroidKeyStore");
  keyStore.load(null);
  PrivateKey privateKey = (PrivateKey) keyStore.getKey("key1", null);
  PublicKey publicKey = keyStore.getCertificate("key1").getPublicKey();
  </code>

Example: RSA key pair for signing/verification using RSA-PSS

This example illustrates how to generate an RSA key pair in the Android KeyStore system under alias key1 authorized to be used only for signing using the RSA-PSS signature padding scheme with SHA-256 or SHA-512 digests. The use of the public key is unrestricted.

<code>KeyPairGenerator keyPairGenerator = KeyPairGenerator.getInstance(
          KeyProperties.KEY_ALGORITHM_RSA, "AndroidKeyStore");
  keyPairGenerator.initialize(
          new KeyGenParameterSpec.Builder(
                  "key1",
                  KeyProperties.PURPOSE_SIGN)
                  .setDigests(KeyProperties.DIGEST_SHA256, KeyProperties.DIGEST_SHA512)
                  .setSignaturePaddings(KeyProperties.SIGNATURE_PADDING_RSA_PSS)
                  .build());
  KeyPair keyPair = keyPairGenerator.generateKeyPair();
  Signature signature = Signature.getInstance("SHA256withRSA/PSS");
  signature.initSign(keyPair.getPrivate());
  ...
 
  // The key pair can also be obtained from the Android Keystore any time as follows:
  KeyStore keyStore = KeyStore.getInstance("AndroidKeyStore");
  keyStore.load(null);
  PrivateKey privateKey = (PrivateKey) keyStore.getKey("key1", null);
  PublicKey publicKey = keyStore.getCertificate("key1").getPublicKey();
  </code>

Example: RSA key pair for encryption/decryption using RSA OAEP

This example illustrates how to generate an RSA key pair in the Android KeyStore system under alias key1 where the private key is authorized to be used only for decryption using RSA OAEP encryption padding scheme with SHA-256 or SHA-512 digests. The use of the public key is unrestricted.

<code>KeyPairGenerator keyPairGenerator = KeyPairGenerator.getInstance(
          KeyProperties.KEY_ALGORITHM_RSA, "AndroidKeyStore");
  keyPairGenerator.initialize(
          new KeyGenParameterSpec.Builder(
                  "key1",
                  KeyProperties.PURPOSE_DECRYPT)
                  .setDigests(KeyProperties.DIGEST_SHA256, KeyProperties.DIGEST_SHA512)
                  .setEncryptionPaddings(KeyProperties.ENCRYPTION_PADDING_RSA_OAEP)
                  .build());
  KeyPair keyPair = keyPairGenerator.generateKeyPair();
  Cipher cipher = Cipher.getInstance("RSA/ECB/OAEPWithSHA-256AndMGF1Padding");
  cipher.init(Cipher.DECRYPT_MODE, keyPair.getPrivate());
  ...
 
  // The key pair can also be obtained from the Android Keystore any time as follows:
  KeyStore keyStore = KeyStore.getInstance("AndroidKeyStore");
  keyStore.load(null);
  PrivateKey privateKey = (PrivateKey) keyStore.getKey("key1", null);
  PublicKey publicKey = keyStore.getCertificate("key1").getPublicKey();
  </code>

Example: AES key for encryption/decryption in GCM mode

The following example illustrates how to generate an AES key in the Android KeyStore system under alias key2 authorized to be used only for encryption/decryption in GCM mode with no padding.

<code>KeyGenerator keyGenerator = KeyGenerator.getInstance(
          KeyProperties.KEY_ALGORITHM_AES, "AndroidKeyStore");
  keyGenerator.init(
          new KeyGenParameterSpec.Builder("key2",
                  KeyProperties.PURPOSE_ENCRYPT | KeyProperties.PURPOSE_DECRYPT)
                  .setBlockModes(KeyProperties.BLOCK_MODE_GCM)
                  .setEncryptionPaddings(KeyProperties.ENCRYPTION_PADDING_NONE)
                  .build());
  SecretKey key = keyGenerator.generateKey();
 
  Cipher cipher = Cipher.getInstance("AES/GCM/NoPadding");
  cipher.init(Cipher.ENCRYPT_MODE, key);
  ...
 
  // The key can also be obtained from the Android Keystore any time as follows:
  KeyStore keyStore = KeyStore.getInstance("AndroidKeyStore");
  keyStore.load(null);
  key = (SecretKey) keyStore.getKey("key2", null);
  </code>

Example: HMAC key for generating a MAC using SHA-256

This example illustrates how to generate an HMAC key in the Android KeyStore system under alias key2 authorized to be used only for generating an HMAC using SHA-256.

<code>KeyGenerator keyGenerator = KeyGenerator.getInstance(
          KeyProperties.KEY_ALGORITHM_HMAC_SHA256, "AndroidKeyStore");
  keyGenerator.init(
          new KeyGenParameterSpec.Builder("key2", KeyProperties.PURPOSE_SIGN).build());
  SecretKey key = keyGenerator.generateKey();
  Mac mac = Mac.getInstance("HmacSHA256");
  mac.init(key);
  ...
 
  // The key can also be obtained from the Android Keystore any time as follows:
  KeyStore keyStore = KeyStore.getInstance("AndroidKeyStore");
  keyStore.load(null);
  key = (SecretKey) keyStore.getKey("key2", null);
  </code>

Example: EC key for ECDH key agreement

This example illustrates how to generate an elliptic curve key pair, used to establish a shared secret with another party using ECDH key agreement.

<code>KeyPairGenerator keyPairGenerator = KeyPairGenerator.getInstance(
          KeyProperties.KEY_ALGORITHM_EC, "AndroidKeyStore");
  keyPairGenerator.initialize(
          new KeyGenParameterSpec.Builder(
              "eckeypair",
              KeyProperties.PURPOSE_AGREE_KEY)
              .setAlgorithmParameterSpec(new ECGenParameterSpec("secp256r1"))
              .build());
  KeyPair myKeyPair = keyPairGenerator.generateKeyPair();
 
  // Exchange public keys with server. A new ephemeral key MUST be used for every message.
  PublicKey serverEphemeralPublicKey; // Ephemeral key received from server.
 
  // Create a shared secret based on our private key and the other party's public key.
  KeyAgreement keyAgreement = KeyAgreement.getInstance("ECDH", "AndroidKeyStore");
  keyAgreement.init(myKeyPair.getPrivate());
  keyAgreement.doPhase(serverEphemeralPublicKey, true);
  byte[] sharedSecret = keyAgreement.generateSecret();
 
  // sharedSecret cannot safely be used as a key yet. We must run it through a key derivation
  // function with some other data: "salt" and "info". Salt is an optional random value,
  // omitted in this example. It's good practice to include both public keys and any other
  // key negotiation data in info. Here we use the public keys and a label that indicates
  // messages encrypted with this key are coming from the server.
  byte[] salt = {};
  ByteArrayOutputStream info = new ByteArrayOutputStream();
  info.write("ECDH secp256r1 AES-256-GCM-SIV\0".getBytes(StandardCharsets.UTF_8));
  info.write(myKeyPair.getPublic().getEncoded());
  info.write(serverEphemeralPublicKey.getEncoded());
 
  // This example uses the Tink library and the HKDF key derivation function.
  AesGcmSiv key = new AesGcmSiv(Hkdf.computeHkdf(
          "HMACSHA256", sharedSecret, salt, info.toByteArray(), 32));
  byte[] associatedData = {};
  return key.decrypt(ciphertext, associatedData);
  </code>

Summary

Nested classes
	`Builder` Builder of `KeyGenParameterSpec` instances.

Public methods
AlgorithmParameterSpec?	`getAlgorithmParameterSpec()` Returns the key algorithm-specific `AlgorithmParameterSpec` that will be used for creation of the key or `null` if algorithm-specific defaults should be used.
String?	`getAttestKeyAlias()` Returns the alias of the attestation key that will be used to sign the attestation certificate of the generated key.
ByteArray!	`getAttestationChallenge()` Returns the attestation challenge value that will be placed in attestation certificate for this key pair.
Array<String!>	`getBlockModes()` Gets the set of block modes (e.g.,
Date	`getCertificateNotAfter()` Returns the end date to be used on the X.
Date	`getCertificateNotBefore()` Returns the start date to be used on the X.
BigInteger	`getCertificateSerialNumber()` Returns the serial number to be used on the X.
X500Principal	`getCertificateSubject()` Returns the subject distinguished name to be used on the X.
Array<String!>	`getDigests()` Returns the set of digest algorithms (e.g.,
Array<String!>	`getEncryptionPaddings()` Returns the set of padding schemes (e.g.,
Int	`getKeySize()` Returns the requested key size.
Date?	`getKeyValidityForConsumptionEnd()` Returns the time instant after which the key is no longer valid for decryption and verification or `null` if not restricted.
Date?	`getKeyValidityForOriginationEnd()` Returns the time instant after which the key is no longer valid for encryption and signing or `null` if not restricted.
Date?	`getKeyValidityStart()` Returns the time instant before which the key is not yet valid or `null` if not restricted.
String	`getKeystoreAlias()` Returns the alias that will be used in the `java.security.KeyStore` in conjunction with the `AndroidKeyStore`.
Int	`getMaxUsageCount()` Returns the maximum number of times the limited use key is allowed to be used or `KeyProperties.UNRESTRICTED_USAGE_COUNT` if there’s no restriction on the number of times the key can be used.
MutableSet<String!>	`getMgf1Digests()` Returns the set of digests that can be used by the MGF1 mask generation function (e.g.,
Int	`getPurposes()` Returns the set of purposes (e.g., encrypt, decrypt, sign) for which the key can be used.
Array<String!>	`getSignaturePaddings()` Gets the set of padding schemes (e.g.,
Int	`getUserAuthenticationType()` Gets the modes of authentication that can authorize use of this key.
Int	`getUserAuthenticationValidityDurationSeconds()` Gets the duration of time (seconds) for which this key is authorized to be used after the user is successfully authenticated.
Boolean	`isDevicePropertiesAttestationIncluded()` Returns `true` if attestation for the base device properties (`Build.BRAND`, `Build.DEVICE`, `Build.MANUFACTURER`, `Build.MODEL`, `Build.PRODUCT`) was requested to be added in the attestation certificate for the generated key.
Boolean	`isDigestsSpecified()` Returns `true` if the set of digest algorithms with which the key can be used has been specified.
Boolean	`isInvalidatedByBiometricEnrollment()` Returns `true` if the key is irreversibly invalidated when a new biometric is enrolled or all enrolled biometrics are removed.
Boolean	`isMgf1DigestsSpecified()` Returns `true` if the set of digests for the MGF1 mask generation function, with which the key can be used, has been specified.
Boolean	`isRandomizedEncryptionRequired()` Returns `true` if encryption using this key must be sufficiently randomized to produce different ciphertexts for the same plaintext every time.
Boolean	`isStrongBoxBacked()` Returns `true` if the key is protected by a Strongbox security chip.
Boolean	`isUnlockedDeviceRequired()` Returns `true` if the key is authorized to be used only while the device is unlocked.
Boolean	`isUserAuthenticationRequired()` Returns `true` if the key is authorized to be used only if the user has been authenticated.
Boolean	`isUserAuthenticationValidWhileOnBody()` Returns `true` if the key will remain authorized only until the device is removed from the user's body, up to the validity duration.
Boolean	`isUserConfirmationRequired()` Returns `true` if the key is authorized to be used only for messages confirmed by the user.
Boolean	`isUserPresenceRequired()` Returns `true` if the key is authorized to be used only if a test of user presence has been performed between the `Signature.initSign()` and `Signature.sign()` calls.

KeyGenParameterSpec

Known issues

Example: NIST P-256 EC key pair for signing/verification using ECDSA

Example: RSA key pair for signing/verification using RSA-PSS

Example: RSA key pair for encryption/decryption using RSA OAEP

Example: AES key for encryption/decryption in GCM mode

Example: HMAC key for generating a MAC using SHA-256

Example: EC key for ECDH key agreement

Summary

Public methods

getAlgorithmParameterSpec

getAttestKeyAlias

getAttestationChallenge

getBlockModes

getCertificateNotAfter

getCertificateNotBefore

getCertificateSerialNumber

getCertificateSubject

getDigests

getEncryptionPaddings

getKeySize

getKeyValidityForConsumptionEnd

getKeyValidityForOriginationEnd

getKeyValidityStart

getKeystoreAlias

getMaxUsageCount

getMgf1Digests

getPurposes

getSignaturePaddings

getUserAuthenticationType

getUserAuthenticationValidityDurationSeconds

isDevicePropertiesAttestationIncluded

isDigestsSpecified

isInvalidatedByBiometricEnrollment

isMgf1DigestsSpecified

isRandomizedEncryptionRequired

isStrongBoxBacked

isUnlockedDeviceRequired

isUserAuthenticationRequired

isUserAuthenticationValidWhileOnBody

isUserConfirmationRequired

isUserPresenceRequired