(Token Exchange Service): Doesn't respond to port configuration properly.

[ChilloManiac]

Describe the bug
When there's already a deployed TokenExchangeService, and there's a need to assign it a static port, it will initially not respond to that settings-change until it is forcefully rebooted.

To Reproduce

1. Deploy the TokenExchanceService with no configuration
2. Deploy the TokenExchangeService with port: 2020 or other number.

Expected behavior
The TokenExchanceService should start serving on the configured port.

Actual behavior
The TokenExchangeService keeps serving on the original port. Inspecting the configuration with the greengrass-cli it has

{ "actualPort": <oldPort>, "port": <newPort> }

Using cURL, its apparent that the oldport is the one still serving traffic, while the new one does not.

The only way i've made it actually use the port is

1. Rebooting device
2. Restarting nucleus
3. Removing and Adding the TES component

Environment

• OS: RHEL 9.5
• JDK version: openjdk 11.0.25 2024-10-15 LTS
• Nucleus version: 2.12.6

Additional information:
Also the docs at Greengrass does not specify the port can be set. You have to see the README.md for the TES in this repo

[junfuchen99]

Hello, thank you for reporting this issue.

You are correct - when changing the TES port configuration, a nucleus restart is required for the changes to take effect. This behavior occurs because the TES URI is distributed to components via environment variable at component startup and cannot be dynamically updated while components are running.

We will update our documentation and look into improving this. See #1691

[saranyailla]

Thank you for your patience. Closing this issue as the fix for this bug is now available in Nucleus 2.14.3.