[GitHub] [jclouds] gaul commented on pull request #64: JCLOUDS-1520 - Reuse SSLSocketFactory in JavaUrlHttpCommandExecutorSe…

[GitBox]

gaul commented on PR #64:
URL: https://github.com/apache/jclouds/pull/64#issuecomment-1204555122

   Closing due to inactivity.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@jclouds.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jclouds] gaul closed pull request #64: JCLOUDS-1520 - Reuse SSLSocketFactory in JavaUrlHttpCommandExecutorSe…

[GitBox]

gaul closed pull request #64: JCLOUDS-1520 - Reuse SSLSocketFactory in 
JavaUrlHttpCommandExecutorSe…
URL: https://github.com/apache/jclouds/pull/64


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@jclouds.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jclouds] gaul merged pull request #152: Upgrade to jax-rs 2.1.1

[GitBox]

gaul merged PR #152:
URL: https://github.com/apache/jclouds/pull/152


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@jclouds.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Jenkins build is back to stable : JClouds » jclouds #62

[Apache Jenkins Server]

See 

[GitHub] [jclouds] gaul opened a new pull request, #152: Upgrade to jax-rs 2.1

[GitBox]

gaul opened a new pull request, #152:
URL: https://github.com/apache/jclouds/pull/152

   Also address constant TODO.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@jclouds.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Resolved] (JCLOUDS-1616) Proxy credentials validation is missing in OkHttpCommandExecutorService API request

[Andrew Gaul (Jira)]

 [ 
https://issues.apache.org/jira/browse/JCLOUDS-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Gaul resolved JCLOUDS-1616.
--
Fix Version/s: 2.6.0
   Resolution: Fixed

> Proxy credentials validation is missing in OkHttpCommandExecutorService API 
> request
> ---
>
> Key: JCLOUDS-1616
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1616
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-drivers
>Reporter: Anand
>Priority: Major
>  Labels: okhttp
> Fix For: 2.6.0
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> Hi,
> In our project, Azure ComputeServiceContext is constructed with proxy setting 
> properties (includes credentials) as below,
> overrides.setProperty(Constants.*PROPERTY_PROXY_HOST*, "...");
> overrides.setProperty(Constants.*PROPERTY_PROXY_PORT*, "..");
> overrides.setProperty(Constants.*PROPERTY_PROXY_TYPE*, 
> Proxy.Type.HTTP.name());
> overrides.setProperty(Constants.*PROPERTY_PROXY_USER*, "...");
> overrides.setProperty(Constants.*PROPERTY_PROXY_PASSWORD*, "...");
> ComputeServiceContext context = 
> ContextBuilder.newBuilder("azurecompute-arm").credentials(identity, 
> credential)
>   
> .overrides(overrides).buildView(ComputeServiceContext.class);
> When the API request is called, OkHttpCommandExecutorService.invoke method 
> doesn't populate the credentials in the proxyAuthenticator during 
> okHttpClient builder.
> Therefore  validation of credentials is ignored.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (JCLOUDS-1616) Proxy credentials validation is missing in OkHttpCommandExecutorService API request

[Andrew Gaul (Jira)]

 [ 
https://issues.apache.org/jira/browse/JCLOUDS-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Gaul updated JCLOUDS-1616:
-
Affects Version/s: 2.5.0

> Proxy credentials validation is missing in OkHttpCommandExecutorService API 
> request
> ---
>
> Key: JCLOUDS-1616
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1616
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-drivers
>Affects Versions: 2.5.0
>Reporter: Anand
>Priority: Major
>  Labels: okhttp
> Fix For: 2.6.0
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> Hi,
> In our project, Azure ComputeServiceContext is constructed with proxy setting 
> properties (includes credentials) as below,
> overrides.setProperty(Constants.*PROPERTY_PROXY_HOST*, "...");
> overrides.setProperty(Constants.*PROPERTY_PROXY_PORT*, "..");
> overrides.setProperty(Constants.*PROPERTY_PROXY_TYPE*, 
> Proxy.Type.HTTP.name());
> overrides.setProperty(Constants.*PROPERTY_PROXY_USER*, "...");
> overrides.setProperty(Constants.*PROPERTY_PROXY_PASSWORD*, "...");
> ComputeServiceContext context = 
> ContextBuilder.newBuilder("azurecompute-arm").credentials(identity, 
> credential)
>   
> .overrides(overrides).buildView(ComputeServiceContext.class);
> When the API request is called, OkHttpCommandExecutorService.invoke method 
> doesn't populate the credentials in the proxyAuthenticator during 
> okHttpClient builder.
> Therefore  validation of credentials is ignored.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (JCLOUDS-1616) Proxy credentials validation is missing in OkHttpCommandExecutorService API request

[Andrew Gaul (Jira)]

 [ 
https://issues.apache.org/jira/browse/JCLOUDS-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Gaul updated JCLOUDS-1616:
-
Labels: okhttp  (was: )

> Proxy credentials validation is missing in OkHttpCommandExecutorService API 
> request
> ---
>
> Key: JCLOUDS-1616
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1616
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-drivers
>Reporter: Anand
>Priority: Major
>  Labels: okhttp
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> Hi,
> In our project, Azure ComputeServiceContext is constructed with proxy setting 
> properties (includes credentials) as below,
> overrides.setProperty(Constants.*PROPERTY_PROXY_HOST*, "...");
> overrides.setProperty(Constants.*PROPERTY_PROXY_PORT*, "..");
> overrides.setProperty(Constants.*PROPERTY_PROXY_TYPE*, 
> Proxy.Type.HTTP.name());
> overrides.setProperty(Constants.*PROPERTY_PROXY_USER*, "...");
> overrides.setProperty(Constants.*PROPERTY_PROXY_PASSWORD*, "...");
> ComputeServiceContext context = 
> ContextBuilder.newBuilder("azurecompute-arm").credentials(identity, 
> credential)
>   
> .overrides(overrides).buildView(ComputeServiceContext.class);
> When the API request is called, OkHttpCommandExecutorService.invoke method 
> doesn't populate the credentials in the proxyAuthenticator during 
> okHttpClient builder.
> Therefore  validation of credentials is ignored.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (JCLOUDS-1616) Proxy credentials validation is missing in OkHttpCommandExecutorService API request

[Andrew Gaul (Jira)]

 [ 
https://issues.apache.org/jira/browse/JCLOUDS-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Gaul updated JCLOUDS-1616:
-
Component/s: (was: jclouds-core)

> Proxy credentials validation is missing in OkHttpCommandExecutorService API 
> request
> ---
>
> Key: JCLOUDS-1616
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1616
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-drivers
>Reporter: Anand
>Priority: Major
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> Hi,
> In our project, Azure ComputeServiceContext is constructed with proxy setting 
> properties (includes credentials) as below,
> overrides.setProperty(Constants.*PROPERTY_PROXY_HOST*, "...");
> overrides.setProperty(Constants.*PROPERTY_PROXY_PORT*, "..");
> overrides.setProperty(Constants.*PROPERTY_PROXY_TYPE*, 
> Proxy.Type.HTTP.name());
> overrides.setProperty(Constants.*PROPERTY_PROXY_USER*, "...");
> overrides.setProperty(Constants.*PROPERTY_PROXY_PASSWORD*, "...");
> ComputeServiceContext context = 
> ContextBuilder.newBuilder("azurecompute-arm").credentials(identity, 
> credential)
>   
> .overrides(overrides).buildView(ComputeServiceContext.class);
> When the API request is called, OkHttpCommandExecutorService.invoke method 
> doesn't populate the credentials in the proxyAuthenticator during 
> okHttpClient builder.
> Therefore  validation of credentials is ignored.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [jclouds] gaul commented on pull request #151: JCLOUDS-1616: Proxy credentials validation is missing in OkHttpComman…

[GitBox]

gaul commented on PR #151:
URL: https://github.com/apache/jclouds/pull/151#issuecomment-1203882912

   Thank you for your contribution @SATYANAN-ANAND!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@jclouds.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (JCLOUDS-1616) Proxy credentials validation is missing in OkHttpCommandExecutorService API request

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/JCLOUDS-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17574700#comment-17574700
 ] 

ASF subversion and git services commented on JCLOUDS-1616:
--

Commit 88f0c341cfc4a6508db63794846e7c3902b8e255 in jclouds's branch 
refs/heads/master from SATYANAN-ANAND
[ https://gitbox.apache.org/repos/asf?p=jclouds.git;h=88f0c341cf ]

JCLOUDS-1616: Proxy credentials validation is missing in 
OkHttpCommandExecutorService API request

Added support for credentials validation


> Proxy credentials validation is missing in OkHttpCommandExecutorService API 
> request
> ---
>
> Key: JCLOUDS-1616
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1616
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-core, jclouds-drivers
>Reporter: Anand
>Priority: Major
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Hi,
> In our project, Azure ComputeServiceContext is constructed with proxy setting 
> properties (includes credentials) as below,
> overrides.setProperty(Constants.*PROPERTY_PROXY_HOST*, "...");
> overrides.setProperty(Constants.*PROPERTY_PROXY_PORT*, "..");
> overrides.setProperty(Constants.*PROPERTY_PROXY_TYPE*, 
> Proxy.Type.HTTP.name());
> overrides.setProperty(Constants.*PROPERTY_PROXY_USER*, "...");
> overrides.setProperty(Constants.*PROPERTY_PROXY_PASSWORD*, "...");
> ComputeServiceContext context = 
> ContextBuilder.newBuilder("azurecompute-arm").credentials(identity, 
> credential)
>   
> .overrides(overrides).buildView(ComputeServiceContext.class);
> When the API request is called, OkHttpCommandExecutorService.invoke method 
> doesn't populate the credentials in the proxyAuthenticator during 
> okHttpClient builder.
> Therefore  validation of credentials is ignored.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [jclouds] gaul merged pull request #151: JCLOUDS-1616: Proxy credentials validation is missing in OkHttpComman…

[GitBox]

gaul merged PR #151:
URL: https://github.com/apache/jclouds/pull/151


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@jclouds.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jclouds] gaul merged pull request #149: Upgrade testng to 7.5

[GitBox]

gaul merged PR #149:
URL: https://github.com/apache/jclouds/pull/149


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@jclouds.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org