JarCasting
EOSIO SDK for Java: Android Keystore Signature Provider
Android Keystore Signature Provider is an example pluggable signature provider for EOSIO SDK for Java written in Kotlin. It allows for signing transactions using Android Keystore keys.
All product and company names are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.
Contents
- About Signature Providers
- Prerequisites
- Installation
- Basic Usage
- Android Example App
- Library Methods
- Releases
- Want to Help?
- Important
About Signature Providers
The Signature Provider abstraction is arguably the most useful of all of the EOSIO SDK for Java providers. It is responsible for:
- finding out what keys are available for signing (
getAvailableKeys), and - requesting and obtaining transaction signatures with a subset of the available keys (
signTransaction).
By simply switching out the signature provider on a transaction, signature requests can be routed any number of ways.
All signature providers must conform to the ISignatureProvider Protocol.
Prerequisites
- Android (minimum SDK version 23, compile SDK version 29, target SDK version 29)
- Kotlin 1.3.31+
- Gradle 4.10.1+
Since EOSIO SDK for Java: Android Keystore Signature Provider is an Android specific project, we recommend using Android Studio if you are going to work on it.
Installation
This provider is intended to be used in conjunction with EOSIO SDK for Java as a provider plugin.
To use Android Keystore Signature Provider with EOSIO SDK for Java in your app, add the following modules to your build.gradle:
implementation 'one.block:eosiojava:1.0.0'
implementation 'one.block:eosioandroidkeystoresignatureprovider:1.0.0'
If you are using Android Keystore Signature Provider (or any library that depends on it) in an Android application, you must also add the following to your application's build.gradle file in the android section:
// Needed to get bitcoin-j to produce a valid apk for android.
packagingOptions {
exclude 'lib/x86_64/darwin/libscrypt.dylib'
exclude 'lib/x86_64/freebsd/libscrypt.so'
exclude 'lib/x86_64/linux/libscrypt.so'
}
The build.gradle files for the project currently include configurations for publishing the project to Artifactory. These should be removed if you are not planning to use Artifactory or you will encounter build errors. To do so, make the changes marked by comments throughout the files.
Then refresh your gradle project. Then you're all set for the Basic Usage example!
Basic Usage
Generally, signature providers are called by the TransactionProcessor during signing. (See an example here.) If you find, however, that you need to get available keys or request signing directly, this library can be invoked as follows:
val eosioAndroidKeyStoreSignatureProvider: EosioAndroidKeyStoreSignatureProvider =
EosioAndroidKeyStoreSignatureProvider.Builder().build()
val allKeysInKeyStore: List<String> = eosioAndroidKeyStoreSignatureProvider.availableKeys
And to generate a private key:
val isKeyCreated:Boolean = EosioAndroidKeyStoreUtility.generateKeyInAndroidStore("key_alias")
To sign an EosioTransactionSignatureRequest, you should first create it with your serialized transaction and list of public keys. EOSIO SDK for Java handles the creation of the object for you.
Finally, call signTransaction to sign.
val transactionSignatureRequest: EosioTransactionSignatureRequest =
EosioTransactionSignatureRequest(
serializedTransaction,
signingPublicKeys,
chainID,
abis,
isModifiable
)
val eosioAndroidKeyStoreSignatureProvider: EosioAndroidKeyStoreSignatureProvider =
EosioAndroidKeyStoreSignatureProvider.Builder().build()
eosioAndroidKeyStoreSignatureProvider.signTransaction(transactionSignatureRequest)
Android Example App
If you'd like to see an example implementation that uses a different Signature Provider, check out our open source Android Example App--a working application that fetches an account's token balance and pushes a transfer action.
Library Methods
This library is an example implementation of ISignatureProvider. It implements the following protocol methods:
signTransaction(EosioTransactionSignatureRequest eosioTransactionSignatureRequest)signs aTransactiongetAvailableKeys()returns an array containing the public keys associated with the private keys that the object is initialized with
The library also includes a utility class that allows the user to manage keys in the Android Keystore (e.g., query, add, or delete). Key management includes the ability to add password protection and use user-defined aliases to label and query the keys. The keys that are queried are automatically converted to the EOS format so that they are automatically compatible with EOS mainnet applications. The class is called EosioAndroidKeyStoreUtility and can be referenced as follows:
Generate a key by calling:
EosioAndroidKeyStoreUtility.generateAndroidKeyStoreKey(alias:String)
Query all keys in Keystore by calling:
EosioAndroidKeyStoreUtility.getAllAndroidKeyStoreKeysInEOSIOFormat(password: KeyStore.ProtectionParameter?, loadStoreParameter: KeyStore.LoadStoreParameter?)
Query a specific key in the Keystore by calling:
EosioAndroidKeyStoreUtility.getAndroidKeyStoreKeyInEOSIOFormat(alias: String, password: KeyStore.ProtectionParameter?, loadStoreParameter: KeyStore.LoadStoreParameter?)
Sign any data with a specific key in the Keystore by calling:
EosioAndroidKeyStoreUtility.sign(data: ByteArray, alias: String, password: KeyStore.ProtectionParameter?, loadStoreParameter: KeyStore.LoadStoreParameter?)
Delete a key in the Keystore by its alias by calling:
EosioAndroidKeyStoreUtility.deleteKeyByAlias(keyAliasToDelete: String, loadStoreParameter: KeyStore.LoadStoreParameter?)
Delete all keys in the Keystore by calling:
EosioAndroidKeyStoreUtility.deleteAllKeys(loadStoreParameter: KeyStore.LoadStoreParameter?)
Releases
11/05/2020
Version 1.0.0 This version consumes the new eosio-java library version 1.0.0.
2/27/20
Version 0.1.1 The version consumes the new eosio-java library version 0.1.2.
Want to help?
Interested in contributing? That's awesome! Here are some Contribution Guidelines and the Code of Conduct.
Important
See LICENSE for copyright and license terms.
All repositories and other materials are provided subject to the terms of this IMPORTANT notice and you must familiarize yourself with its terms. The notice contains important information, limitations and restrictions relating to our software, publications, trademarks, third-party resources, and forward-looking statements. By accessing any of our repositories and other materials, you accept and agree to the terms of the notice.
