`aws_credentials_provider_new_chain_default` hangs without ever calling credentialsCallBack

[awslabs]

`aws_credentials_provider_new_chain_default` hangs without ever calling credentialsCallBack

[TingDaoK]

Can you please share some log? You can enable log by adding

#include <aws/io/logging.h>

struct aws_logger_standard_options options = {
    .level = AWS_LL_TRACE,
    .file = stderr,
};
struct aws_logger logger;
aws_logger_init_standard(&logger, allocator, &options);
aws_logger_set(&logger);

Also, will it hang if you set up tls_ctx and still call aws_credentials_provider_new_chain_default instead?

[daniel347x]

Thanks again for looking into this!

(1) I attempted to enable logging, as you've indicated.

Unfortunately, though the code you provided to enable logging successfully builds, at runtime it segfaults. (Also, my version of the C++ compiler did not allow initialization of structs in the way your code does it, so it's a bit modified.)

Here is my logger initialization:

As noted, the above code builds, but at runtime, I see the "Logging for AWS set up" in the console, but then it segfaults.

Do you have any suggestions to prevent the segfault?

(2) I modified the code as you suggested (and as I knew you might ask). Here is my current code:

As you can see, I have (a) initialized a TLS struct; and (b) called 'aws_credentials_provider_new_chain_default', passing it the TLS struct.

Exactly the same hang occurs. The program simply hangs forever, at the same place I indicated previously.

Please let me know if there is anything else I can do to assist.

Thanks!

[TingDaoK]

Can you share the runtime segfault info, so that we can help to find out why you get the segfault?

For your info, @waahm7 has set up the environment as you did, but we cannot reproduce the issue from our end.
We verified that the aws_credentials_provider_new_chain_default works well with sts_web_identity.

As we cannot reproduce the issue from our end, and we don't have any logs here to track through what's happening for you, we cannot do anything yet. So, please, provide the segfault info that we can try to help you to get the logs.

Here is my guess:

• It's probably hanging from your aws_credentials_provider_new_profile, which is the second one in the chain, so that STS web identity never invoked. But, without details, we don't know why it's hanging still. And, of cause, it should never hang
• for the segfault, have you called aws_auth_library_init()?

[github-actions]

Greetings! It looks like this issue hasn’t been active in longer than a week. We encourage you to check if this is still an issue in the latest release. Because it has been longer than a week since the last update on this, and in the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or add an upvote to prevent automatic closure, or if the issue is already closed, please feel free to open a new one.