Re: Handling Self Signed Certs

2013-06-11 Thread Mike Tutkowski
, download manager, API module to hypervisor > >>hosts > >> > >>have > >> > >> the similar situation. > >> > >> > >> > >> > >> > >> Kelven > >> > >> > >> > >> On 6/6

Re: Handling Self Signed Certs

2013-06-11 Thread Kelven Yang
gt; > >> >> > >> >> > >> Kelven >> > >> >> > >> On 6/6/13 2:33 PM, "Soheil Eizadi" wrote: >> > >> >> > >> >What is missing is a facility to import a certificate into the >>store. >> >

Re: Handling Self Signed Certs

2013-06-11 Thread Will Stevens
>> >should be part of GUI to add devices. > > >> > > > >> >I am implementing a similar HTTP Client. You are using > > >>DefaultHttpClient > > >> >so it is based on the newer Apache libraries. The ones I found in > > >>

Re: Handling Self Signed Certs

2013-06-11 Thread Mike Tutkowski
ar HTTP Client. You are using > >>DefaultHttpClient > >> >so it is based on the newer Apache libraries. The ones I found in > >> >CloudStack were older Commons HttpClient which was EOL. > >> > > >> >In my case I planned to wrap the Clie

Re: Handling Self Signed Certs

2013-06-10 Thread Kelven Yang
was EOL. >> > >> >In my case I planned to wrap the Client as you have for development and >> >for production have an API to import a certificate for SSL into the >> >Certificate Store. >> > >> >I would call to AuthScope(host, 443) to limit access to only the >>specific >>

Re: Handling Self Signed Certs

2013-06-10 Thread Chiradeep Vittal
was EOL. >> > >> >In my case I planned to wrap the Client as you have for development and >> >for production have an API to import a certificate for SSL into the >> >Certificate Store. >> > >> >I would call to AuthScope(host, 443) to limit access to only the >>speci

Re: Handling Self Signed Certs

2013-06-10 Thread Will Stevens
>-Soheil > > > >From: williamstev...@gmail.com [williamstev...@gmail.com] on behalf of > >Will Stevens [wstev...@cloudops.com] > >Sent: Thursday, June 06, 2013 1:08 PM > >To: dev@cloudstack.apache.org > >Subject: Re: Handling

Re: Handling Self Signed Certs

2013-06-06 Thread Kelven Yang
gt; >-Soheil > >From: williamstev...@gmail.com [williamstev...@gmail.com] on behalf of >Will Stevens [wstev...@cloudops.com] >Sent: Thursday, June 06, 2013 1:08 PM >To: dev@cloudstack.apache.org >Subject: Re: Handling Self Signed Certs > >He

RE: Handling Self Signed Certs

2013-06-06 Thread Soheil Eizadi
only the specific host and port. -Soheil From: williamstev...@gmail.com [williamstev...@gmail.com] on behalf of Will Stevens [wstev...@cloudops.com] Sent: Thursday, June 06, 2013 1:08 PM To: dev@cloudstack.apache.org Subject: Re: Handling Self Signed Certs

Re: Handling Self Signed Certs

2013-06-06 Thread Will Stevens
Hey Kelven, I am using the same https client libraries as elsewhere in Cloudstack (well one of them because there is more than one version of http client libs currently available in CS). I am using this client: import org.apache.http.impl.client.DefaultHttpClient; I initialize it like this: _http

Re: Handling Self Signed Certs

2013-06-06 Thread Kelven Yang
Will, We have several other integrated components that have the similar situation, it makes sense to consolidate the HTTPS client we used across CloudStack and have a global configuration to deal with self-signed certificate for all in testing or POC. To help testing/POC process to be smooth, we

Handling Self Signed Certs

2013-06-06 Thread Will Stevens
Hey All, I am building integration between CS and an external Palo Alto Firewall device. The API calls to the PA device are done over HTTPS. In some cases (like testing or a POC), it makes sense to use a self signed cert for this connection. Currently I have a little http client wrapper which al