-
Notifications
You must be signed in to change notification settings - Fork 899
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for the OIDCScope configuration parameter #19858
Comments
@abellotti Was this part of the recent PR? (and thus closable?) |
Oh...didn't realize this was for appliance_console cli |
This issue has been automatically marked as stale because it has not been updated for at least 3 months. If you can still reproduce this issue on the current release or on Thank you for all your contributions! More information about the ManageIQ triage process can be found in the traige process documentation. |
This issue has been automatically marked as stale because it has not been updated for at least 3 months. If you can still reproduce this issue on the current release or on Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation. |
There are tons of OpenID-Connect configuration parameters we could be considering for OOTB support with mod_auth_openidc in Apache, as seen here in https://github.com/zmartzone/mod_auth_openidc/blob/master/auth_openidc.conf.
While customers can manually update the manageiq-external-auth-openidc.conf file in the /etc/httpd/conf.d directory on the appliance, template for that file being here: https://github.com/ManageIQ/manageiq-appliance/blob/master/TEMPLATE/etc/httpd/conf.d/manageiq-external-auth-openidc.conf.erb, we like to minimize the need to manually update those.
One parameter we can add support for is the
OIDCScope
. While for our testing the default scope ofopenid
is sufficient, customers may need to add additional scopes as some of the claims we require as shown here https://github.com/ManageIQ/manageiq-appliance/blob/master/TEMPLATE/etc/httpd/conf.d/manageiq-remote-user-openidc.confare only sent by the Identity Provider via the additional scopes defined.
This RFE is to add support for the OIDC Scope parameter in ManageIQ. This includes the following updates:
The template itself:
https://github.com/ManageIQ/manageiq-appliance/blob/master/TEMPLATE/etc/httpd/conf.d/manageiq-external-auth-openidc.conf.erb
Adding the configurable parameter:
The updated documentation for manual configuration mentioning the new parameter and the default
openid
:The Appliance console CLI for configuring the new parameter:
https://github.com/ManageIQ/manageiq-appliance_console/blob/master/lib/manageiq/appliance_console/oidc_authentication.rb
Adding the optional:
as optional parameter, and defaulting to
openid
if not specified.We also need to update the config map generator for the ManageIQ httpd pod accordingly:
https://github.com/ManageIQ/httpd_configmap_generator/blob/master/README-oidc.md
https://github.com/ManageIQ/httpd_configmap_generator/blob/master/lib/httpd_configmap_generator/oidc.rb
Adding support for the optional:
Making sure the
auth-oidc-scope
parameter is defined for the template to consume.Would need to update the Podified HTTPD Container's template accordingly to add the OIDCScope parameter:
Finally, when we generate a JWT token in the API in theget_jwt_token
method shown here:- https://github.com/ManageIQ/manageiq-api/blob/95e86abb70c2a601f424e18f3d8d0f3d119c9d01/app/controllers/api/base_controller/authentication.rb#L230We need to pass the scope as fetched from the config file to the Identity Provider's token_endpoint so we get the optional claims defined for the appliance/- Implemented here: ManageIQ/manageiq-api#747The text was updated successfully, but these errors were encountered: