until an HTTP request is received. A downside of lazy initialization is that it can delay the discovery of a problem with the application. If a misconfigured bean is initialized lazily, a failure will @ServletComponentScan has no effect in a standalone container, where the container’s built-in discovery mechanisms are used instead. The ServletWebServerApplicationContext Under the hood, Spring Boot user-name-attribute: "name" For OpenID Connect providers that support OpenID Connect discovery, the configuration can be further simplified. The provider needs to be configured with an issuer-uri

until an HTTP request is received. A downside of lazy initialization is that it can delay the discovery of a problem with the application. If a misconfigured bean is initialized lazily, a failure will @ServletComponentScan has no effect in a standalone container, where the container’s built-in discovery mechanisms are used instead. The ServletWebServerApplicationContext Under the hood, Spring Boot user-name-attribute: "name" For OpenID Connect providers that support OpenID Connect discovery, the configuration can be further simplified. The provider needs to be configured with an issuer-uri

until an HTTP request is received. A downside of lazy initialization is that it can delay the discovery of a problem with the application. If a misconfigured bean is initialized lazily, a failure will @ServletComponentScan has no effect in a standalone container, where the container’s built-in discovery mechanisms are used instead. The ServletWebServerApplicationContext Under the hood, Spring Boot user-name-attribute: "name" For OpenID Connect providers that support OpenID Connect discovery, the configuration can be further simplified. The provider needs to be configured with an issuer-uri

until an HTTP request is received. A downside of lazy initialization is that it can delay the discovery of a problem with the application. If a misconfigured bean is initialized lazily, a failure will @ServletComponentScan has no effect in a standalone container, where the container’s built-in discovery mechanisms are used instead. The ServletWebServerApplicationContext Under the hood, Spring Boot user-name-attribute: "name" For OpenID Connect providers that support OpenID Connect discovery, the configuration can be further simplified. The provider needs to be configured with an issuer-uri

until an HTTP request is received. A downside of lazy initialization is that it can delay the discovery of a problem with the application. If a misconfigured bean is initialized lazily, a failure will @ServletComponentScan has no effect in a standalone container, where the container’s built-in discovery mechanisms are used instead. The ServletWebServerApplicationContext Under the hood, Spring Boot user-name-attribute: "name" For OpenID Connect providers that support OpenID Connect discovery, the configuration can be further simplified. The provider needs to be configured with an issuer-uri

until an HTTP request is received. A downside of lazy initialization is that it can delay the discovery of a problem with the application. If a misconfigured bean is initialized lazily, a failure will @ServletComponentScan has no effect in a standalone container, where the container’s built-in discovery mechanisms are used instead. The ServletWebServerApplicationContext Under the hood, Spring Boot user-name-attribute: "name" For OpenID Connect providers that support OpenID Connect discovery, the configuration can be further simplified. The provider needs to be configured with an issuer-uri

until an HTTP request is received. A downside of lazy initialization is that it can delay the discovery of a problem with the application. If a misconfigured bean is initialized lazily, a failure will @ServletComponentScan has no effect in a standalone container, where the container’s built-in discovery mechanisms are used instead. The ServletWebServerApplicationContext Under the hood, Spring Boot user-name-attribute: "name" For OpenID Connect providers that support OpenID Connect discovery, the configuration can be further simplified. The provider needs to be configured with an issuer-uri

until an HTTP request is received. A downside of lazy initialization is that it can delay the discovery of a problem with the application. If a misconfigured bean is initialized lazily, a failure will @ServletComponentScan has no effect in a standalone container, where the container’s built-in discovery mechanisms are used instead. The ServletWebServerApplicationContext Under the hood, Spring Boot user-name-attribute: "name" For OpenID Connect providers that support OpenID Connect discovery, the configuration can be further simplified. The provider needs to be configured with an issuer-uri

until an HTTP request is received. A downside of lazy initialization is that it can delay the discovery of a problem with the application. If a misconfigured bean is initialized lazily, a failure will @ServletComponentScan has no effect in a standalone container, where the container’s built-in discovery mechanisms are used instead. The ServletWebServerApplicationContext Under the hood, Spring Boot user-name-attribute: "name" For OpenID Connect providers that support OpenID Connect discovery, the configuration can be further simplified. The provider needs to be configured with an issuer-uri

until an HTTP request is received. A downside of lazy initialization is that it can delay the discovery of a problem with the application. If a misconfigured bean is initialized lazily, a failure will @ServletComponentScan has no effect in a standalone container, where the container’s built-in discovery mechanisms are used instead. The ServletWebServerApplicationContext Under the hood, Spring Boot user-name-attribute: "name" For OpenID Connect providers that support OpenID Connect discovery, the configuration can be further simplified. The provider needs to be configured with an issuer-uri