I have found the answer.
It is, indeed, the JDBC Driver that's taking care of this.
The driver provided by MySQL has a few options/flags for secure channel
control.
On Fri, Sep 24, 2010 at 7:52 AM, Arthur Yeo <artyyeo_at_gmail.com> wrote:
> As an aside, let's assume that MySQL has SSL turned ON.
>
> But, the MySQL client (in our case, the RESTful WS) needs to know SSL.
>
> If I set up MySQL as a rsrc in GF and have it registered as a pooled rsrc
> (with the right JDBC connection string including the SSL port), how would
> that stack up?
> Does it mean that when my Java code grabs a JDBC connection, it will be
> automatically be communicating in a secure channel? It seemed like the JDBC
> driver has to know that.
>
> Am I heading the right path?
>
>
> On Thu, Sep 23, 2010 at 8:41 PM, Arthur Yeo <artyyeo_at_gmail.com> wrote:
>
>> Hi everyone,
>>
>> Hope you guys had fun at JavaOne 2010.
>>
>> Now, I have been successful in establishing SSL channels between external
>> browsers and GF (where my WebServices [WS] live).
>> But, I also need to secure the communications between my POJO code in my
>> RESTful WS talking to MySQL.
>>
>> Browser <--> WS(GF) <--> MySQL
>>
>> Is there a way to make the communications between WS(GF) <--> MySQL go
>> thru SSL ? Can GF/Jersey help with this?
>>
>> Or do I need to link my POJO code with some SSL lib and handle all the SSL
>> comm myself?
>>
>> --
>> Arthur Y.
>>
>
>
>
> --
> Arthur Y.
>
--
Arthur Y.