Bug 1902316 - [RFE] Integrate AZURE AD as an Identity Provider using Keystone's Federation. [NEEDINFO]
Summary: [RFE] Integrate AZURE AD as an Identity Provider using Keystone's Federation.
Keywords:
Status: CLOSED DUPLICATE of bug 1590932
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-keystone
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Dave Wilde
QA Contact: Jeremy Agee
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-27 17:14 UTC by Pierre-Andre MOREY
Modified: 2023-08-03 15:46 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-10 21:22:53 UTC
Target Upstream Version:
Embargoed:
ifrangs: needinfo? (dwilde)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-198 0 None None None 2021-11-10 20:14:57 UTC

Description Pierre-Andre MOREY 2020-11-27 17:14:41 UTC
Description of problem:

We have a Telco customer, who uses Azure AD as a solution for authentication and users management and he would like to have keystone able to use it as a provider.


RHOSP 16.1.2

It seems that Azure AD supports OpenID.

Regards,
Pierre-André

Comment 4 Oskari Lemmela 2021-03-23 13:44:04 UTC
We noticed one configuration parameter which needs to be added to keystone httpd configuration to allow azure pass more than 5 groups in token.

Settings OIDCResponseMode "form_post" allows bigger tokens to be sent. Currently there is no way to set this parameters via puppet parameters.

Azure also uses jwks to verify tokens. following puppet parameters need to be added to configuration

ExtraConfig:
  keystone::federation::openidc::openidc_verify_method: jwks
  keystone::federation::openidc::openidc_verify_jwks_uri: https://login.microsoftonline.com/{{ azure_auth_tenant }}/discovery/v2.0/keys
  keystone::federation::openidc::openidc_claim_delimiter: ";"


Note You need to log in before you can comment on or make changes to this bug.