From 8bb6d25cf3b6d9e51ae5e2cabfa50c9a364e8842 Mon Sep 17 00:00:00 2001
From: Ghanshyam Mann <gmann@ghanshyammann.com>
Date: Wed, 21 Jul 2021 14:21:01 -0500
Subject: [PATCH] Update git submodules

* Update django_openstack_auth from branch 'master'
  to 031814a7bd81dd9a79a5070e7b37ce825fd13c7f
  - Moving IRC network reference to OFTC

    Change-Id: Ib811fb321d18fc01f3786f8b3ab16b2eda558864

  - Revert "Prepare transitional DOA package"

    This reverts commit aa06f462a6f74312289705f0da41ac5c2a549693.

    We finally did not release the transitional package,
    so the previous commit has no meaning.

    Change-Id: I03f53dc45ec5c425863ac7278f2fb1a0d9a298f2

  - Prepare transitional DOA package

    It was suggested to create a new major version (which will be 4.0.0)
    of DOA as a transitional package to stop providing any module itself.

    http://lists.openstack.org/pipermail/openstack-dev/2018-January/126431.html

    Queens release of horizon is planned to depend on the new DOA release.

    Part of blueprint merge-openstack-auth
    Change-Id: I3776fedcf21c1b4d669fede478f58518d489f0ef

  - Retire project

    In Queens development cycle, openstack_auth code was merged
    into the horizon repository.

    blueprint merge-openstack-auth

    Change-Id: I74b10a90fe79fc768cfb8de6f68d3cd2f4938e51

  - Don't add required attribute to html form fields

    In Django 1.10 a new Form property was introduced, defaulting to True,
    which enabled HTML form validation for fields marked "required" in
    Django. This changed old behavior, which was that required fields were
    only validated server-side. This patch restores old behavior by setting
    use_required_attribute to False for the inherited AuthenticationForm.

    This problem arose because when WebSSO is enabled and a
    non-keystone-credentials authentication method is selected from the
    dropdown list, the now-hidden username and password fields are still
    marked "required" and still validated client-side, even though they are
    invisible to the user and cannot be filled in. It would be nice to fix
    the javascript to properly turn the "required" attribute on or off
    depending on what authentication method is selected and whether the
    "required" fields are even visible, but for now this just restores the
    behavior we had before Djanto 1.10.

    Change-Id: I3e798a2288d9c33396b40a86b07ea8c163d3b525
    Closes-bug: #1703109

  - Imported Translations from Zanata

    For more information about this automatic import see:
    https://docs.openstack.org/i18n/latest/reviewing-translation-import.html

    Change-Id: Idf5ecc6044c4470cf4496fe7ca1eda2ee1e99679

  - Merge "Imported Translations from Zanata"
  - Updated from global requirements

    Change-Id: Ia77c55d2d92f90c693a8b0925c02a4b2cd6e9f18

  - Imported Translations from Zanata

    For more information about this automatic import see:
    https://docs.openstack.org/i18n/latest/reviewing-translation-import.html

    Change-Id: Idc03c122787afcb1f3ba7d8ab630e0a15b5848a5
---
 django_openstack_auth | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/django_openstack_auth b/django_openstack_auth
index 58e881ec93..031814a7bd 160000
--- a/django_openstack_auth
+++ b/django_openstack_auth
@@ -1 +1 @@
-Subproject commit 58e881ec93b9803141c0f519da2e8142183a10ab
+Subproject commit 031814a7bd81dd9a79a5070e7b37ce825fd13c7f