Closed roryodonnell closed 2 years ago
@IBMeric - any insight would be greatly appreciated
Must have been something to do with connection properties / service availability - seems all good now
We never seemed to discover the original cause and now we are experiencing it again. It would be great if the sdk could provide further information why the credentials.token
is not populated. It's most likely a service issue caused by IBM Cloud COS Auth servers
Ok have finally discovered the cause. Our COS API key was not being seeding correctly from vault and thus was using an empty string when trying to connect.
Hitting an auth issue whilst checking for a COS bucket - I'm unsure if it's a self inflicted issue or not - please feel free to close if not due to COS SDK