Turns out the problem was that azureblob doesn’t honor CredentialSupplier like aws-s3. We changed to using CredentialSupplier instead of passing a Credential and the username and password never make it into the context.
Easy to fix - hard to find. Thanks for the quick response. John On Tue, Jul 2, 2024 at 7:19 PM Andrew Phillips <[email protected]> wrote: > > but still digging through that. > > Looks like ExpandProperties is where this happens: > > > https://github.com/apache/jclouds/blob/master/core/src/main/java/org/jclouds/functions/ExpandProperties.java > > Given that this hasn't changed and probably isn't broken given how > widely it's used, my first question would be whether the > "jclouds.azureblob.account" property is set and available to jclouds > somehow? > > Regards > > ap >
