User Guide

http.reauth
Plugin

A common basis for authenticating with various and multiple authentication systems.

This came to be as we wanted to dynamically authenticate our docker registry against gitlab-ci and avoid storing credentials in gitlab while still permitting users to log in with their own credentials.

Full documentation

Examples

Configuration
reauth { path /v2 simple username=password,root=badpractice upstream url=https://accounts.example.com/check gitlab url=https://gitlab.example.com/ }

Authenticate access against /v2 with the following flow (in this order) 1 does the username and password match any of the given comma seperated credentials 2 basic http auth against https://accounts.example.com/check 3 against a gitlab project with the gitlab-ci-token user (docker login docker.example.com -u "$CIPROJECTPATH" -p "$CIBUILDTOKEN")

Related Links
Documentation

Access the full documentation for this plugin off-site:

Docs
Plugin Help

Get help from the maintainers of the http.reauth plugin:

Support
Plugin Website

Visit http.reauth's website for more information:

Website
Plugin Author: Freman
Last Updated: 13 Jul 2017, 10:52 PM
This plugin is independent of the Caddy project and is not endorsed or maintained by Caddy developers. Use at your own risk. Do not file issues for this plugin on Caddy's bug tracker.