podman login with Azure AD credentials doesn't work

From Brian Coursen via nmartins@redhat.com :

https://access.redhat.com/support/cases/#/case/03203616
What problem/issue/behavior are you having trouble with?  What do you expect to see?
We’re trying to push an Execution Environment to our private Automation Hub. There are a few local accounts in this Hub, but the required method is to using SAML (via Red Hat SSO). When pushing with the local account, the action succeeds. When using the SAML account (from Azure AD), the action fails with the following errors:
(cut errors out, can send)
*****
CU is expecting that AD accounts get populated in a manner that allows account to login in via podman login <automationhub_repo>. 

I believe this is working as intended. Need to verify with engineering team.
*****
Both Matt and I are still unable to login via podman to the Automation Hub from Controller. However, just as a test, we did create a new "local" account in SSO (not sourced from Azure AD), granted it the hubadmin role, and were able to podman login using that account. The problem appears to be with the AD accounts only.
******
Good morning, Michael. We've completed the upgrade to 2.1.2, but we still cannot login with podman. Please let me know what I should do next.
******
Hello! Yes, I can verify the credentials the user is entering are valid, as they can login to the UI with the same username and password. I'm a Red Hat consultant, as is the user that's actually trying to perform the action.

However, we're now in the process of upgrading AAP to 2.1.2. This was recommended for another issue we were having - but with Automation Controller. Once Hub & SSO are upgraded, we will run the test again and report back on this case.
—
It sounds like this was implemented and working (via dnewswan who initially implemented it), but has since stopped.