You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, configuring OIDC in ood_portal.yml generates an absolute path for the OIDC redirect URI in the resulting httpd configuration file.
For example:
This works fine in most circumstances, however if one or more server aliases are also specified, then OIDC doesn't work correctly for the alias URLs, since only one URL is populated for the OIDCRedirectURI field in the httpd config.
Removing the fqdn (OIDCRedirectURI /oidc) fixes this. mod_auth_openidc has supported relative paths since 2017 (relevant PR here: OpenIDC/mod_auth_openidc#259).
Could we add a configuration option to generate relative paths for the OIDCRedirectURI option in ood-portal.yml? This would grant better support for multiple server aliases.
The text was updated successfully, but these errors were encountered:
By default, configuring OIDC in
ood_portal.yml
generates an absolute path for the OIDC redirect URI in the resultinghttpd
configuration file.For example:
This works fine in most circumstances, however if one or more server aliases are also specified, then OIDC doesn't work correctly for the alias URLs, since only one URL is populated for the
OIDCRedirectURI
field in thehttpd
config.Removing the fqdn (
OIDCRedirectURI /oidc
) fixes this.mod_auth_openidc
has supported relative paths since 2017 (relevant PR here: OpenIDC/mod_auth_openidc#259).Could we add a configuration option to generate relative paths for the
OIDCRedirectURI
option inood-portal.yml
? This would grant better support for multiple server aliases.The text was updated successfully, but these errors were encountered: