No description, website, or topics provided.
Clone or download
kthblmfld and nadiabahrami Adds ldap query script used for testing changes in AD
Adds support for paging results

Signed-off-by: keithbloomfield <>
Latest commit 3ce92bb Dec 12, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/ISSUE_TEMPLATE Added Agnes' task issue template Sep 7, 2018
.travis Updated to reset data Oct 5, 2018
bin Adds ldap query script used for testing changes in AD Dec 13, 2018
chatbot Add bot pack request functionality Dec 10, 2018
client Add approved requests screen Dec 10, 2018
docker Removes next provider from the project Dec 12, 2018
docs Adds the ldap sequence diagram (and src) to Sphinx docs Dec 12, 2018
rbac Added missing LDAP Fields for transform Dec 12, 2018
tests Adding ldap validation tests Dec 10, 2018
ui Rename plural message actions Nov 19, 2018
windows-dependencies complete all environment set up Dec 3, 2018
.dockerignore Don't ignore protobufs on docker copy Oct 23, 2018
.env.example Hardening LDAP provider Dec 9, 2018
.gitattributes Address Rasa NLU issue Dec 7, 2018
.gitignore Setting up non-interactive client id with AAD Oct 18, 2018
.readthedocs.yml Repaired local Sphinx docs build. Hoping it repairs published docs Dec 7, 2018
.travis.yml Add lint to Travis Nov 26, 2018 Merging Requirements files Nov 1, 2018
LICENSE Add Apache 2.0 LICENSE file Aug 18, 2018 Proposing adding Adam G. as maintainer Oct 12, 2018 Add role and task test helpers Nov 18, 2018
config.yaml Common configuration Dec 1, 2018
docker-compose.yaml Removes next provider from the project Dec 12, 2018
docker-multi-node.yaml Uniform Dockerfiles Oct 26, 2018
docker-persist.yaml Updating all licenses Oct 12, 2018
docker-test.yaml Add server (API), rethink and ledgersync to test docker config Nov 15, 2018
lint.tmp Aligns Python paths in the IDE Oct 12, 2018
logo.png Replaces logos with valid binaries Nov 5, 2018
pytest.ini Adding tests and fixing format Nov 6, 2018
requirement.local.txt Remove sanic-oauth dependency Nov 5, 2018
requirements.txt Repaired local Sphinx docs build. Hoping it repairs published docs Dec 7, 2018
setup.cfg Add AAD delta outbound user and group sync Nov 13, 2018
strict.cfg Add role and task test helpers Nov 18, 2018


Hyperledger Sawtooth NEXT Identity Platform

Build Status License Documentation Status

This repo contains multiple components which together with a Hyperledger Sawtooth validator, will comprise the "blockchain" components of the NEXT Identity Platform project. The components include:

  • a server which provides a REST API for querying blockchain data
  • a transaction processor which handles RBAC-specific transaction logic
  • a ledger sync which writes blockchain state changes to a local database


The easiest way to run these components is with Docker. To start these components, first install Docker for your platform and clone this repo.

Docker volume mounts must be enabled, to allow docker to mount the repository files.

To build and deploy the app, run:

docker-compose up

A shortcut is available via:


This will build all components, start them in individual Docker containers, and download and run the necessary Sawtooth components.

To stop the containers, hit Ctrl-C and then:

docker-compose down

A shortcut is available via:


Persistent Data

By default, the data in the development environment is ephemeral. It will be lost when the application is stopped and restarted.

To enable persistent data, use the -p flag:

bin/start -p

To delete the persistent data, delete the related docker volumes:

To clear data and start again from genesis, delete the volumes: docker volume ls docker volume rm {folder_name}_chain docker volume rm {folder_name}_keys docker volume rm {folder_name}_db


One may tell docker to rebuild the containers, using the the --build flag. This may be useful if dependencies have changed in a way docker did not detect.

docker-compose up --build

A shortcut is available via:

bin/start -b

To do a hard rebuild by first removing all cached docker volumes and python caches, run:



System Dependencies

The server code is written in python 3. Confirm your version using command:

python -V

For information in setting up your development environment, visit:

Deploying Multi-Node Network

The multi-node network consists of four nodes (more can be added) hosting Sawtooth Next Directory. The multi-node network utilizes the PoET simulator consensus between the validators allowing PoET to run on non-SGX hardware.

After starting the containers, the Next Directory UI will be available at:

To start the containers in a multi-node configuration run:

docker-compose -f docker-multi-node.yaml up

Deploying to Any Non-Localhost Server

Pay special attention to the notes about secret keys in .env. Due to their private/sensitive nature, the values of these keys should be provided to the application using

  • a configuration file that is not stored/managed by git
  • cli arguments
  • some other means that prevents them from being publicly available

They are the most sensitive components for the security of your application. Manage them wisely and responsibly.

When no such keys are provided, random keys are generated on application bootstrap to simplify development. This avoids publication of the keys in git and allows the application to start up in their absence. Work is underway to cause startup to fail fast and explosively when keys are missing. Once that work is complete, the random key generation can be removed as well. In other words: It must be made obvious to a user when startup fails due to missing keys.


Preparing Unit Tests

If you are unit testing a feature having a new Pip dependency in it, then add the new dependency to tests.Dockerfile to ensure it is available in the test runtime.

Populating Test Data

To quickly populate the application with test users, roles, etc., run script bin/ once the application is up and running. It will spin up a rest client and create the objects through the application's rest api.

Running Automated Tests

Library test can be run using (pytest)[]:

pytest -m "library"

Integration tests can be run non-interactively via the run_docker_test script, with the desired docker-compose file as an argument. For example:

bin/run_docker_test docker-tests.yaml

A shortcut is available via:

bin/build -t

They can be run interactively from the rbac-shell:

docker exec -it rbac-shell bash

Cleaning the Docker Image Cache

Docker-compose relies on image caching to improve build and deployment time. Some changes (directory renaming, etc) can cause the loading of cached images to result in build failures in docker-compose. In addition, not shutting down containers properly by doing a docker-compose down also leads to this scenario. When it occurs, you will experience hanging in the legacy UI and stack traces from rbac_server:

 Traceback (most recent call last):
rbac-server    |   File "/usr/local/lib/python3.5/dist-packages/sanic/", line 556, in handle_request
rbac-server    |     response = await response
rbac-server    |   File "/usr/lib/python3.5/asyncio/", line 105, in __next__
rbac-server    |     return self.gen.send(None)
rbac-server    |   File "/project/hyperledger-rbac/server/api/", line 74, in create_new_user
rbac-server    |, txn_key.public_key, private_key.as_bytes()
rbac-server    |   File "/project/hyperledger-rbac/server/api/", line 172, in encrypt_private_key
rbac-server    |     cipher =, AES.MODE_CBC, init_vector)
rbac-server    | ValueError: non-hexadecimal number found in fromhex() arg at position 30

To work around this situation, shut down the application, delete all containers and images, and rebuild/deploy:


docker rm -vf $(docker ps -a -q)

docker rmi -f $(docker images -a -q)

bin/start -b 


Hyperledger Sawtooth NEXT Identity Platform software is licensed under the Apache License Version 2.0 software license.


Big Thanks

Cross-browser Testing Platform and Open Source <3 Provided by Sauce Labs