Description of changes:
When using authentication type AWS_LAMBDA and providing the token as () => Promise<string> there is the possibility that the Promise is rejected.
The Promise is awaited with the call await this._awsRealTimeHeaderBasedAuth outside of any try catch block. This lead to a "Unhandled rejected promise" exception.
By moving the call into the existing try-catch block a rejected token Promise will be handled gracefully.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Issue #, if available:
Description of changes: When using authentication type AWS_LAMBDA and providing the token as
() => Promise<string>there is the possibility that the Promise is rejected. The Promise is awaited with the callawait this._awsRealTimeHeaderBasedAuthoutside of any try catch block. This lead to a "Unhandled rejected promise" exception. By moving the call into the existing try-catch block a rejected token Promise will be handled gracefully.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.