[BUG] DefaultContextResolver is not using defaultRealm value from the PolarisApplicationConfig

[almazgalievisl]

Is this a possible security vulnerability?

• This is NOT a possible security vulnerability

Describe the bug

PolarisApplicationConfig defines defaultRealm and allows overriding it trough configuration file. DefaultContextResolver ignores a value from the configuration.

To Reproduce

0. Setup an eclipse link with a database name which is different from default-realm
1. Set defaultRealm in the configuration yaml file
2. Try to connect to get the token without setting realm explicitly in the request's headers
3. Polaris returns an error:

FATAL: database 'default-realm' does not exist

Actual Behavior

Configuration setting is not a source of truth for the all components

Expected Behavior

Configuration setting defines a default value for the all components

Additional context

No response

System information

No response

[loicalleyne]

I came across the same issue, but since this error is thrown when the realm is incorrect or the bearer token is missing perhaps it could also indicate an attempt at unauthorized access. Either way the message returned could be clearer.