[
https://issues.apache.org/jira/browse/JCLOUDS-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17204652#comment-17204652
]
Blagoi Anastasov commented on JCLOUDS-1553:
-------------------------------------------
It worked when adding .overrides(stsProperties) to the STSApi:
STSApi api = ContextBuilder.newBuilder({color:#9876aa}STS_API{color})
.modules(modulesBuilder.build())
.overrides(stsProperties)
.credentialsSupplier(() ->
{color:#b389c5}credentials{color}).buildApi(STSApi.{color:#cc7832}class{color}){color:#cc7832};
stsProperties:
{color}
{color:#cc7832} jclouds:proxy-port -> 1000
jclouds.endpoint ->
[https://sts.amazonaws.com|https://sts.amazonaws.com/] - This is very
important! If it is not sts but s3.amazonaws.com, it will not work!
jclouds.proxy-type -> SOCKS
jclouds.proxy-host -> 10.10.10.10{color}
> STSApi does not go through proxy
> --------------------------------
>
> Key: JCLOUDS-1553
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1553
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
> Affects Versions: 2.2.0
> Reporter: Blagoi Anastasov
> Priority: Major
>
> STSApi does not understand that the server uses a proxy. And the connection
> does not go through the proxy.
> STSApi api = ContextBuilder.newBuilder({color:#9876aa}STS_API{color})
> .modules(modulesBuilder.build())
> .credentialsSupplier(() ->
> {color:#b389c5}credentials{color}).buildApi(STSApi.{color:#cc7832}class{color}){color:#cc7832};{color}
> api.assumeRole({color:#9876aa}ROLE_ARN{color}{color:#cc7832},{color}{color:#9876aa}STS_SESSION_NAME{color}{color:#cc7832},
> {color}getAssumeRoleOptions()){color:#cc7832};
> {color:#172b4d}Also if .overrides() is added to the STSApi with properties
> that consists of information about the proxy, it fails again with different
> error:{color}{color}
> Query-string authentication requires the Signature, Expires and
> AWSAccessKeyId parameters
> {color:#cc7832} {color}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
