So that I don't get this message.
Can we add instructions to the message so we don't get stuck here
That's a non-blocking warning intended to help catch typos in the Directory Server hostname, if that's where the LFDSSTS instance you want to use is. The value determines the LFDSSTS URL where Repository Web Client redirects users to for authentication. The value can be any valid LFDSSTS URL, DNS aliased, separate STS instance from LFDS, etc. It's not required to match what's in the license file.
The warning's wording causes lots of confusion but it's just a basic string check of the hostname in the URL against the LFDS hostname in the app's license file. You can't get "stuck" there, as in the warning doesn't block the config from saving.
With current version, the LFDS hostname in license file will always be FQDN of the LFDS machine. In the coming Fall 2025 release, we have added the ability to change that.
After installed Fall 2025 release, you can add `<add name="TokenIssuer" value="lfds.example.com" />` to LFDS.exe.config/appsettings.
And if you have multiple license sites, you can run "INSERT INTO db_settings (name, value) values('tokenissuer', 'lfds.example.com')" in database.
The FQDN of the LFDS machine is what I want to use. It is forcing me to use the PQDN and it is impossible to buy a certificate for a partial name.
IE:
I want to use "https://server.domain.com"
It will only take "https://server"
They also have Forms and it has not problem using https://server.domain.com with the same LFDS server.
That's a non-blocking warning intended to help catch typos in the Directory Server hostname, if that's where the LFDSSTS instance you want to use is. The value determines the LFDSSTS URL where Repository Web Client redirects users to for authentication. The value can be any valid LFDSSTS URL, DNS aliased, separate STS instance from LFDS, etc. It's not required to match what's in the license file.
The warning's wording causes lots of confusion but it's just a basic string check of the hostname in the URL against the LFDS hostname in the app's license file. You can't get "stuck" there, as in the warning doesn't block the config from saving.
Ah for some reason I thought it was not allowing me to click save yesterday. Today I tried again and it worked. If it is just a warning that is no problem, was misleading I guess.