From 589a383eb6d8e4c1344041d480c447670832ec3d Mon Sep 17 00:00:00 2001 From: Zuul Date: Mon, 7 Jan 2019 22:26:42 +0000 Subject: [PATCH] Update git submodules * Update keystone from branch 'master' - Merge "Add section on configuring protected auth paths" - Add section on configuring protected auth paths Without this change, the federation guide does not do a good job of explaining which URL paths should be protected by a federation-capable auth module and why. Instead, the SP-specific guides give code samples with no context, which makes it confusing to understand how to modify the paths in the examples to fit one's own deployment. This change adds that introduction. Partial-bug: #1793374 Change-Id: I5cf940e0c54e5dd89cd3db810f8b5889a8ddce2e --- keystone | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/keystone b/keystone index 6c73ab543e..53c8b02ec7 160000 --- a/keystone +++ b/keystone @@ -1 +1 @@ -Subproject commit 6c73ab543e67d96e62e128f477ab92e255fb5c6d +Subproject commit 53c8b02ec708ec913150cd38b68f65f005a3bc04