Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FusionAuth was not defaulting search.servers if not defined in config or environment #2507

Closed
robotdan opened this issue Oct 11, 2023 · 1 comment
Assignees
Labels
bug Something isn't working
Milestone

Comments

@robotdan
Copy link
Member

robotdan commented Oct 11, 2023

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

  1. Ensure search.servers is not configured in fusionauth.properties and you have not configured via environment variables either.
  2. 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.

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 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.

@robotdan robotdan added the bug Something isn't working label Oct 11, 2023
@robotdan robotdan self-assigned this Oct 11, 2023
@robotdan robotdan added this to the 1.48.0 milestone Oct 11, 2023
@robotdan robotdan added this to In progress in FusionAuth Issues Oct 11, 2023
@robotdan robotdan moved this from In progress to Code complete in FusionAuth Issues Oct 11, 2023
@robotdan robotdan moved this from Code complete to Delivered in FusionAuth Issues Oct 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
FusionAuth Issues
  
Delivered
Development

No branches or pull requests

1 participant