-
Notifications
You must be signed in to change notification settings - Fork 507
Description
Expected Behavior
The issue minio/minio#10001 thread was closed without providing the final solution.
After getting the access_token from keycloak, passing same to http://localhost:9000?Action=AssumeRoleWithWebIdentity&Version=2011-06-15&WebIdentityToken=access_token and getting the response back as,
<?xml version="1.0" encoding="UTF-8"?> <AssumeRoleWithWebIdentityResponse xmlns="https://sts.amazonaws.com/doc/2011-06-15/"> <AssumeRoleWithWebIdentityResult> <AssumedRoleUser> <Arn></Arn> <AssumeRoleId></AssumeRoleId> </AssumedRoleUser> <Credentials> <AccessKeyId>FT8P56JOXAJDUCWEYWCP</AccessKeyId> <SecretAccessKey>0aIZ6OhJxkvbxYy+9J20llgrV8JRCG+LtzwKkH8h</SecretAccessKey> <Expiration>2020-08-07T06:11:10Z</Expiration> <SessionToken>eyJhbGciOiJIUzUxMiIsInR5cCI6IkpXVCJ9.eyJhY2Nlc3NLZXkiOiJSRVJITlZXOVZYWDRXUTkxTjZYMyIsImFjciI6IjEiLCJhZGRyZXNzIjp7fSwiYXVkIjoiYWNjb3VudCIsImF6cCI6Im1pbmlvIiwiZW1haWwiOiJicmFkQGdtYWlsLmNvbSIsImVtYWlsX3ZlcmlmaWVkIjpmYWxzZSwiZXhwIjoxNTk2NzgwNjcwLCJmYW1pbHlfbmFtZSI6ImJyYWQiLCJnaXZlbl9uYW1lIjoiYnJhZCIsImdyb3VwcyI6WyJvZmZsaW5lX2FjY2VzcyIsInVtYV9hdXRob3JpemF0aW9uIl0sImlhdCI6MTU5Njc4MDM3MCwiaXNzIjoiaHR0cDovL2xvY2FsaG9zdDo4MDgwL2F1dGgvcmVhbG1zL21hc3RlciIsImp0aSI6ImJhOWUzYjEzLWE2NjAtNGNjYi1hZTVmLTk4YWNjZTM3YzY1YyIsIm5hbWUiOiJicmFkIGJyYWQiLCJwb2xpY3kiOiJyZWFkd3JpdGUiLCJwcmVmZXJyZWRfdXNlcm5hbWUiOiJicmFkIiwicmVhbG1fYWNjZXNzIjp7InJvbGVzIjpbIm9mZmxpbmVfYWNjZXNzIiwidW1hX2F1dGhvcml6YXRpb24iXX0sInJlc291cmNlX2FjY2VzcyI6eyJhY2NvdW50Ijp7InJvbGVzIjpbIm1hbmFnZS1hY2NvdW50IiwibWFuYWdlLWFjY291bnQtbGlua3MiLCJ2aWV3LXByb2ZpbGUiXX19LCJzY29wZSI6Im9wZW5pZCBlbWFpbCBwcm9maWxlIHBob25lIGFkZHJlc3MgcG9saWN5IG1pY3JvcHJvZmlsZS1qd3Qgb2ZmbGluZV9hY2Nlc3MiLCJzZXNzaW9uX3N0YXRlIjoiYzdlY2MwZDItZWZiNS00N2NjLThmOTItNmI3OTJhMmI4ZjNiIiwic3ViIjoiMTAzMTJjMjktZWYxYi00OWNmLTg0ZjQtODQ1MGZiNDZkNDM5IiwidHlwIjoiQmVhcmVyIiwidXBuIjoiYnJhZCJ9.LesWLGzRPjpBms1GiF95ESpyYXaDD8pMXqZfPz1FfffFYLmh7BcrBUMXzvvoI8JLnF5nE01f2sX2I7HMsLVdZA</SessionToken> </Credentials> <SubjectFromWebIdentityToken>10312c29-ef1b-49cf-84f4-8450fb46d439</SubjectFromWebIdentityToken> </AssumeRoleWithWebIdentityResult> <ResponseMetadata> <RequestId>1628E74C2FC1C748</RequestId> </ResponseMetadata> </AssumeRoleWithWebIdentityResponse>
But after passing accessKeyID and SecretAccessKey to minio 7.0 Java SDK as,
MinioClient minioClient = new MinioClient("http://localhost:9000","FT8P56JOXAJDUCWEYWCP","0aIZ6OhJxkvbxYy+9J20llgrV8JRCG+LtzwKkH8h");
Or to minio 7.1 Java SDK as,
MinioClient minioClient = MinioClient.builder().endpoint("http://localhost:9000").credentials("FT8P56JOXAJDUCWEYWCP", "0aIZ6OhJxkvbxYy+9J20llgrV8JRCG+LtzwKkH8h"").build();
minioClient.listBuckets();
Getting below error,
Exception in thread "main" java.lang.IllegalArgumentException: unknown error code string 'InvalidTokenId'
at io.minio.Xml.unmarshal(Xml.java:68)
at io.minio.MinioClient.execute(MinioClient.java:1134)
at io.minio.MinioClient.executeGet(MinioClient.java:1311)
at io.minio.MinioClient.listBuckets(MinioClient.java:3123)
at com.misys.dms.Main.main(Main.java:48)
Current Behavior
Possible Solution
Steps to Reproduce (for bugs)
Context
Regression
Your Environment
- Version used (
minio --version): Java SDK 7.0/7.1 - Server setup and configuration:
- Operating System and version (
uname -a):