# Get licensee hash from an Android application

Source: [https://docs.qualcomm.com/doc/80-PV345-88/topic/android_get_licensee_hash_from_an_android_application.html](https://docs.qualcomm.com/doc/80-PV345-88/topic/android_get_licensee_hash_from_an_android_application.html)

Android applications authored by ISVs may require a feature license/certificate restricted by Licensee or ISV hash.

For QTI to issue a feature license/certificate, the SHA-256 hash of the Android application’s signing certificate is required, which is the SHA-256 hash of the DER-formatted X.509 applicatoin signing certificate. This can be obtained using keytool with the –list –v options as follows:

    keytool -exportcert -list -v -alias <isv-key-name> \
    -keystore <path-to-keystore>Copy to clipboard

`<path-to- keystore>` is the file path name where the keystore containing the certificate is. For debug keys, the default is ~/.android/debug.keystore. For release keys, the location is usually specified by the user.

`<isv-key-name>` is the alias name of the key in the keystore that was specified during key generation. The default for debug keys is androiddebugkey.

The part of the output that must be sent to QTI looks like this:

    SHA256:37:B7:E3:7D:AC:D7:99:7D:4B:C4:D6:C2:8B:6F:8F:31:21:5E:\
    9F:D1:AA:70:4F:BC:64:4E:EA:4F:FF:D4:93:19Copy to clipboard

However, the hexadecimal digits of the output will be different.

For information about keytool see: [https://docs.oracle.com/javase/6/docs/technotes/tools/windows/keytool.html](https://docs.oracle.com/javase/6/docs/technotes/tools/windows/keytool.html).

If the application signing certificate is not in keytool, the following OpenSSL command can be used to get the fingerprint:

    openssl x509 –in <isv_cert_file> -fingerprint –sha256Copy to clipboard

If several keys are used for signing Android applications, then several fingerprints can be sent to QTI and bound to the feature license/certificate. However, it is best to avoid providing the fingerprints of debug certificates with unsecured keys, as that will allow the license to be used with any debug signed application.

- **[Get License from Qualcomm](https://docs.qualcomm.com/doc/80-PV345-88/topic/get_license_from_qualcomm.html)**

**Parent Topic:** [License for Application](https://docs.qualcomm.com/doc/80-PV345-88/topic/Generate_license.html)

Last Published: Nov 11, 2024

[Previous Topic
License for Application](https://docs.qualcomm.com/bundle/publicresource/80-PV345-88/topics/Generate_license.md) [Next Topic
Get License from Qualcomm](https://docs.qualcomm.com/bundle/publicresource/80-PV345-88/topics/get_license_from_qualcomm.md)