Azure SSO when configured through UI causing issue after a linux machine restart in docker deployment.

[rmurali-cr]

Affected module UI and Backend

Describe the bug Azure SSO when configured through UI in works. However, after a restart of machine the openmetadata_server service keep on restarting as each time it ends up in error:

java.lang.NullPointerException
        at java.base/java.util.Objects.requireNonNull(Objects.java:233)
        at java.base/java.util.ImmutableCollections$MapN.<init>(ImmutableCollections.java:1193)
        at java.base/java.util.Map.of(Map.java:1431)
        at org.openmetadata.service.security.LocalJwkProvider.<init>(LocalJwkProvider.java:17)
        at org.openmetadata.service.security.MultiUrlJwkProvider.<init>(MultiUrlJwkProvider.java:32)
        at org.openmetadata.service.security.JwtFilter.<init>(JwtFilter.java:126)
        at org.openmetadata.service.socket.SocketAddressFilter.<init>(SocketAddressFilter.java:41)
        at org.openmetadata.service.OpenMetadataApplication.initializeWebsockets(OpenMetadataApplication.java:873)
        at org.openmetadata.service.OpenMetadataApplication.run(OpenMetadataApplication.java:247)
        at org.openmetadata.service.OpenMetadataApplication.run(OpenMetadataApplication.java:162)
        at io.dropwizard.core.cli.EnvironmentCommand.run(EnvironmentCommand.java:66)
        at io.dropwizard.core.cli.ConfiguredCommand.run(ConfiguredCommand.java:98)
        at io.dropwizard.core.cli.Cli.run(Cli.java:78)
        at io.dropwizard.core.Application.run(Application.java:94)
        at org.openmetadata.service.OpenMetadataApplication.main(OpenMetadataApplication.java:927)
INFO [2025-10-29 12:15:14,863] [JettyShutdownThread] i.d.h.HealthCheckManager - delayed shutdown: started (waiting 1 second)

To Reproduce

1. Deploy openmetadata using docker compose yaml file.
2. Start openmetadata.
3. Login as admin.
4. On settings, Choose Azure SSO and Configure.
5. Provide details to configure and save.
6. Login to make sure SSO is working.
7. Restart machine (Entire machine restart is required, not just docker containers).
8. Once restart has completed, check the openmetadata_server logs using docker logs command.

Expected behavior On machine restart openmetadata_server should start normal and be healthy with Azure SSO in place.

Version:

• OS: 14~24.04.1-Ubuntu SMP Fri Oct 3 20:52:11 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
• Python version: comes within docker images
• OpenMetadata version: 1.10.3
• OpenMetadata Ingestion package version: comes within docker images

Additional context

• Deployment Model: Docker Compose
• SSO Provider: Azure SSO (Confidential)
• SSL Enabled: Secure via NginX

[mohityadav766]

@aji-aju please validate

[aji-aju]

I tried to reproduce the issue in OM 1.10.3. But openmetadata_server is starting healthy. @mohityadav766