Keywhiz alternatives and similar libraries
Based on the "Security" category.
Alternatively, view Keywhiz alternatives based on common mentions on social networks and blogs.
-
Keycloak
Open Source Identity and Access Management For Modern Applications and Services -
Cryptomator
Multi-platform transparent client-side encryption of your files in the cloud -
pac4j
Security engine for Java (authentication, authorization, multi frameworks): OAuth, CAS, SAML, OpenID Connect, LDAP, JWT... -
jCasbin
An authorization library that supports access control models like ACL, RBAC, ABAC in Java -
Themis by Cossack Labs
Easy to use cryptographic framework for data protection: secure messaging with forward secrecy and secure data storage. Has unified APIs across 14 platforms. -
OACC Framework
OACC (Object ACcess Control) is an advanced Java Application Security Framework -
Nimbus JOSE+JWT
JSON Web Token (JWT) implementation for Java with support for signatures (JWS), encryption (JWE) and web keys (JWK). -
Vault
Secures, stores, and tightly controls access to tokens, passwords, certificates, API keys, and other secrets. It handles leasing, key revocation, key rolling, and auditing. Through a unified API, users can access an encrypted Key/Value store and network encryption-as-a-service, or generate AWS IAM/STS credentials, SQL/NoSQL databases, X.509 certificates, SSH credentials, and more.
Collect and Analyze Billions of Data Points in Real Time
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of Keywhiz or a related project?
README
Keywhiz
Keywhiz is a system for distributing and managing secrets. For more information, see the website.
Our Protecting infrastructure secrets with Keywhiz blog post is worth reading, as it provides some useful context.
Develop
Keywhiz requires Java 11 and MySQL 5.7 or higher.
See [CONTRIBUTING](CONTRIBUTING.md) for details on submitting patches.
Build Keywhiz:
mvn install
Run Keywhiz:
java -jar server/target/keywhiz-server-*-shaded.jar [COMMAND] [OPTIONS]
Useful commands to get started are migrate
, add-user
and server
. Use with
--help
for a list of all available commands. Use with [COMMAND] --help
to
get help on a particular command.
For example, to run Keywhiz with a mysql database in development mode:
SERVER_JAR="server/target/keywhiz-server-*-shaded.jar"
KEYWHIZ_CONFIG="server/target/classes/keywhiz-development.yaml"
# Initialize dev database
java -jar $SERVER_JAR migrate $KEYWHIZ_CONFIG
# Add an administrative user
java -jar $SERVER_JAR add-user $KEYWHIZ_CONFIG
# Run server
java -jar $SERVER_JAR server $KEYWHIZ_CONFIG
To connect to a running Keywhiz instance, you will need to use the CLI.
An example helper shell script that wraps the keywhiz-cli and sets some default parameters:
#!/bin/sh
# Set the path to a compiled, shaded keywhiz-cli JAR file
KEYWHIZ_CLI_JAR="/path/to/keywhiz-cli-shaded.jar"
KEYWHIZ_SERVER_URL="https://$(hostname):4444"
# Use these flags if you want to specify a non-standard CA trust store.
# Alternatively, in development and testing specify the --devTrustStore
# flag to use the default truststore (DO NOT use this in production, as
# the truststore is checked into Keywhiz' code).
TRUSTSTORE="-Djavax.net.ssl.trustStore=/path/to/ca-bundle.jceks"
TRUSTTYPE="-Djavax.net.ssl.trustStoreType=JCEKS"
java "$TRUSTSTORE" "$TRUSTTYPE" -jar "$KEYWHIZ_CLI_JAR" -U "$KEYWHIZ_SERVER_URL" "$@"
Keywhiz uses jOOQ to talk to its database.
If you made changes to the database model and want to regenerate sources:
mvn install -pl model/ -Pgenerate-jooq-sources
We recommend IntelliJ IDEA for development.
Clients & API
Square also maintains a Keywhiz client implementation called Keysync.
Docker
We ship a [Dockerfile](Dockerfile) for building a Docker container for Keywhiz. Please see the Dockerfile for extra instructions.
License
Keywhiz is under the Apache 2.0 license. See the [LICENSE](LICENSE) file for details.
*Note that all licence references and agreements mentioned in the Keywhiz README section above
are relevant to that project's source code only.