When sts is enabled, LocalEngine fails to aunthenticate, but error INVALID_ACCESS_KEY gets converted to error EACESS as shown in logs below:
s3:list_buckets cache get: name=default.rgw.meta+users.keys+badauth : hit (negative entry)
2023-07-14T13:42:28.672+0530 7fd0da7946c0 5 req 13384521065249685102 0.002000010s s3:list_buckets error reading user info, uid=badauth can't authenticate
2023-07-14T13:42:28.672+0530 7fd0da7946c0 20 req 13384521065249685102 0.002000010s s3:list_buckets rgw::auth::s3::LocalEngine denied with reason=-2028
2023-07-14T13:42:28.672+0530 7fd0da7946c0 20 req 13384521065249685102 0.002000010s s3:list_buckets rgw::auth::s3::AWSAuthStrategy denied with reason=-13
2023-07-14T13:42:28.672+0530 7fd0da7946c0 5 req 13384521065249685102 0.002000010s s3:list_buckets Failed the auth strategy, reason=-13
Whereas when sts is NOT enabled, then error INVALID_ACCESS_KEY remains as is, as shown in logs below:
2023-07-14T13:55:46.339+0530 7fe93279c6c0 5 req 13980072073565935116 0.000000000s s3:list_buckets error reading user info, uid=badauth can't authenticate
2023-07-14T13:55:46.339+0530 7fe93279c6c0 20 req 13980072073565935116 0.000000000s s3:list_buckets rgw::auth::s3::LocalEngine denied with reason=-2028
2023-07-14T13:55:46.339+0530 7fe93279c6c0 20 req 13980072073565935116 0.000000000s s3:list_buckets rgw::auth::s3::AWSAuthStrategy denied with reason=-2028
Need to figure out why the conversion is happening.