Update July 2019: This is a maintained fork of the GUTMA Registry Broker that includes integration with OpenID and OpenID Connect. It uses OAuth tokens to query the registries.
This fork includes significant changes and updates to the GUTMA repository:
- Integration with Identification and Authentication, currently using Auth0 and JWT Tokens
- Updated URL endpoints of login and identity
This uses the Auth0 service to issue OpenID and OpenID Connect tokens to perform authentication and privilages.
Welcome to the registry broker sandbox. This site has three things:
-
Registry Broker Whitepaper, read this first to amiliarize yourself with idea and key concepts behind the broker.
-
This broker deployment queries one working registry with sample data (others can be added). Lets call this registry
registryA, this is a instance of aircraftregistry repository. You can explore operators in this registryA. This registry is queried by this broker. -
The logs in using their email ID in the form and gets a token return that can be queried for status and results.
You can open issues to this repository, review the Landscape document to review the background and look at open issues to look at the current work in progress.
This is a Django project that uses Django, Django Rest Framework, Celery and Redis and can be deployed to for e.g. Heroku or other platforms.
Python 3 is required for this and install dependencies using pip install -r requirements.txt.
Use python manage.py migrate to create the initial database tables locally. It will use the default SQLLite.
Use python manage.py loaddata switchboard/defaultbrokerdata.json to populate initial data.
- You will need a redis install and also celery as a worker queue
- Launch browser to http://localhost:8000/ to launch the Broker
To install the trust bridge components you will need to create a account at Auth0 or other service to issue and manage OAuth Tokens.