Frontend: No listed "Supported OpenID Providers" after upgrade to 7.2.

[elenamplanas]

Hi,

Last week we upgraded our production environment to version 7.2.15
On 6.2 we were testing and configuring oidc authentication with the frontend, and now the button for the provider is missing.

The frontend and webdav configuration is this:

############################################
# Domain: webdav-cta-LSTCAM-https-door03Domain
[webdav-cta-LSTCAM-https-${host.name}Domain]
dcache.java.memory.heap=1024m
webdav.mover.queue=webdav
# Cell: frontend
[webdav-cta-LSTCAM-https-${host.name}Domain/frontend]
frontend.authn.accept-client-cert=true
frontend.authn.protocol=https
frontend.cell.name=frontend
frontend.net.port=8468
frontend.root=/pnfs/pic.es/data/cta/LST/Data
frontend.static!dcache-view.endpoints.webdav=https://webdav-lstcam.pic.es:8458/
frontend.static!dcache-view.oidc-authz-endpoint-list=https://idp.pic.es/auth/realms/cta-azuredirectory/protocol/openid-connect/auth
frontend.static!dcache-view.oidc-client-id-list=dcache-view
frontend.static!dcache-view.oidc-provider-name-list=CTA-azuredirectory
# Cell: webdav
[webdav-cta-LSTCAM-https-${host.name}Domain/webdav]
webdav.allowed.client.origins=https://webdav-lstcam.pic.es:8468
webdav.authn.protocol=https
webdav.authz.allowed-paths=/pnfs/pic.es/data/cta/LST/Data
webdav.authz.anonymous-listing=true
webdav.authz.anonymous-operations=READONLY
webdav.cell.name=WebDAV-CTA-LSTCAM-${host.name}
webdav.net.port=8458
webdav.redirect.allow-https=true
webdav.redirect.on-read=true
webdav.root=/pnfs/pic.es/data/cta/LST/Data
## End webdav-cta-LSTCAM-https-door03Domain
############################################

It was running fine before the upgrade. There are 3 different frontends and in all of them we are facing the same problem.

Is there any change we should do? I've reviewed the default parameters for 7.2 and they remain the same.

Thanks in advance.
Elena

[paulmillar]

Hi Elena,

Could you check whether this is the same problem as reported here:
dCache/dcache-view#267

Note that there's a simple work-around contained in the above link

Cheers,
Paul.

[elenamplanas]

Hi Paul,

Yes! Is the same problem.
The work-around worked and solved the problem.

Thanks!
Elena