This service monitors NATS subjects and then relay published messages to one of the following destinations: REST API or Another pub/sub destination (e.g. NATS, RabbitMQ, Kafka)
For the Relay Service to be able to submit a report to an authenticated URL, the Relay Service would have to be able to first do an Authentication call (eg. providing a configurable username/password), then do a call to the final URL to submit the response.
This Authentication application would ideally be cached as long as the destination token is still valid; handle refresh-token logic, etc. so as to not have to authenticate for every request if the previous token requested could still be valid.
For the Relay Service to be able to submit a report to an authenticated URL, the Relay Service would have to be able to first do an Authentication call (eg. providing a configurable username/password), then do a call to the final URL to submit the response.
This Authentication application would ideally be cached as long as the destination token is still valid; handle refresh-token logic, etc. so as to not have to authenticate for every request if the previous token requested could still be valid.