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
FusionAuth was not defaulting search.servers if not defined in config or environment
Description
When using Elasticsearch (or OpenSearch) you must provide one or more URIs for FusionAuth to use to connect to this service.
If you do not define search.servers in fusionauth.properties or define the environment variable, or other supported configuration value, we are supported to default to http://localhost:9021.
This default value was not being picked up, so if you did omit the configuration as described, start up would fail when we attempted to bootstrap the connection to Elasticsearch.
Affects versions
TBD.
The issue may have been easier to hit starting in 1.29.3 when we commented out the default config in fusinoauth.properties for the search.servers configuration.
But I think the bug has existed longer than this.
Steps to reproduce
Ensure search.servers is not configured in fusionauth.properties and you have not configured via environment variables either.
Start up FusionAuth configured to use Elasticsearch.
Expected behavior
We should default the value to http://localhost:9021 and if we cannot find Elasticsearch running there, if running in development mode, we will prompt you in maintenance mode, and if in production mode (silent mode) we will fail to start up with a proper error instead of a Guice exception.
If the search.servers configuration value was not added to the fusionauth.properties configuration file, and you omit the SEARCH_SERVERS environment value, FusionAuth would fail to start. The correct behavior is for FusionAuth to default to http://localhost:9021.
The text was updated successfully, but these errors were encountered:
FusionAuth was not defaulting search.servers if not defined in config or environment
Description
When using Elasticsearch (or OpenSearch) you must provide one or more URIs for FusionAuth to use to connect to this service.
If you do not define
search.servers
infusionauth.properties
or define the environment variable, or other supported configuration value, we are supported to default tohttp://localhost:9021
.This default value was not being picked up, so if you did omit the configuration as described, start up would fail when we attempted to bootstrap the connection to Elasticsearch.
Affects versions
TBD.
The issue may have been easier to hit starting in
1.29.3
when we commented out the default config infusinoauth.properties
for thesearch.servers
configuration.But I think the bug has existed longer than this.
Steps to reproduce
search.servers
is not configured infusionauth.properties
and you have not configured via environment variables either.Expected behavior
We should default the value to
http://localhost:9021
and if we cannot find Elasticsearch running there, if running in development mode, we will prompt you in maintenance mode, and if in production mode (silent mode) we will fail to start up with a proper error instead of a Guice exception.Community guidelines
All issues filed in this repository must abide by the FusionAuth community guidelines.
Additional context
Add any other context about the problem here.
Release Notes
If the
search.servers
configuration value was not added to thefusionauth.properties
configuration file, and you omit theSEARCH_SERVERS
environment value, FusionAuth would fail to start. The correct behavior is for FusionAuth to default tohttp://localhost:9021
.The text was updated successfully, but these errors were encountered: