HTTP-to-LDAP Gateway
Clone or download
Latest commit 34d6338 Jul 17, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
examples WORKER_PROCESSES in compose example Jun 30, 2018
redap Specs params fixes Jul 3, 2018
tests Improved how schemas are generated Jul 1, 2018
.flaskenv Renamed to Redap Jun 27, 2018
.gitignore Fixes settings ignore Jun 20, 2018
LICENSE init Jun 20, 2018
README.rst Update README.rst Jul 17, 2018
keys.sh Renamed to Redap Jun 27, 2018
requirements.txt Added missing requirements Jun 29, 2018
setup.sh init Jun 20, 2018
uwsgi.ini Renamed to Redap Jun 27, 2018

README.rst

                  __
   ________  ____/ /___ _____
  / ___/ _ \/ __  / __ `/ __ \
 / /  /  __/ /_/ / /_/ / /_/ /
/_/   \___/\__,_/\__,_/ .___/
   HTTP/LDAP Gateway /_/

Adding LDAP support can be time-consuming, tedious and complex — but it doesn't have to be.

Redap is an easily deployable micro-service, providing an API for interacting with LDAP-capable directory servers over HTTP.

Features

Redap was partly inspired by and is conceptually similar to dthree/addict, but comes with more features.

  • RESTful HTTP API
  • API key authorization
  • LDAP debugging
  • Custom schemas
  • LDAP3 Simplified Query Language
  • Docker image with flask, uwsgi and nginx
  • SwaggerUI

Getting started

Check out the wiki for guides, client examples and more.

Author

Robert Wikman <rbw@vault13.org>