Skip to Content
Last modified by Aaron Rosenzweig on 2012/03/19 19:33
From version 19.1
edited by cat4ever
on 2010/11/30 04:23
Change comment: There is no comment for this version
To version 26.1
edited by Kieran Kelleher
on 2008/07/21 17:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Development-SSL requests via https protocol
1 +Web Applications-Development-SSL requests via https protocol
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.cat4ever
1 +XWiki.kieran
Content
... ... @@ -1,6 +1,6 @@
1 1  == Introduction ==
2 2  
3 -Sooner or later you will need to develop WebObjects applications that work with SSL requests over https protocol. If ssl is configured on your deployment server, you can probably just change http to https in the app entry URL and the app will probably just work over https protocol. However if your application requires security, you cannot just depend on your users typing in a URL that begins with https. Also since SSL encryption adds more load to the webserver, you may want decide that just some pages need to be returned securely over https and the rest returned via plain old http. In any case, you may want to or need to set up your local OS X development machine to support https protocol so that you can properly test your application. Note also that setting up ssl for testing can be a far simpler task (and not really secure) than setting up real authentic SSL certificates for use in a production server.
3 +Sooner or later you will need to develop WebObjects applications that work with SSL requests over https protocol. If ssl is configured on your deployment server, you can probably just change http to https in the app entry URL and the app will probably just work over https protocol. However if your application requires security, you cannot just depend on your users typing in a URL that begins with https. Also since SSL encryption adds more load to the webserver, you may want decide that just some pages need to be returned securely over https and the rest returned via plain old http. In any case, you may want to or need to set up your local OS X development machine to support https protocol so that you can properly test your application. This article endeavors to do this in a concise way while referring to 3rd party sources where applicable. Note also that setting up ssl for testing can be a far simpler task (and not really secure) than setting up real authentic SSL certificates for use in a production server.
4 4  
5 5  {{info title="Compatability"}}
6 6  
... ... @@ -10,19 +10,12 @@
10 10  * If you like record and verify your OS config as follows:
11 11  ** $ openssl version
12 12  *** OpenSSL 0.9.8g 19 Oct 2007
13 -** $ httpd \-v
13 +** $ httpd -v
14 14  *** Server version: Apache/2.2.8 (Unix)
15 15  
16 +
16 16  {{/info}}
17 17  
18 -=== References ===
19 -
20 -* [[http://httpd.apache.org/docs/2.0/ssl/ssl_faq.html#selfcert]]
21 -* [[http://homepage.mac.com/kelleherk/iblog/C463983418/E683365024/index.html]]
22 -* [[http://www.macosxhints.com/article.php?story=20080628074917113]]
23 -* [[http://www.macosxhints.com/article.php?story=20041129143420344]]
24 -* [[http://developer.apple.com/internet/serverside/modssl.html]]
25 -
26 26  == Development via Apache Webserver ==
27 27  
28 28  By default, WebObjects development installations typically run via DirectConnect. For https development, we must run thru the apache webserver built in to every OS X machine. So before going any further, configure your WebObjects development environment so that your development application launches and [[runs thru apache>>Development Tools-Running Through Apache]] using the host name "localhost".
... ... @@ -31,28 +31,19 @@
31 31  
32 32  === Make the private key and SSL certificate ===
33 33  
34 -Normally creating SSL certificates for production use is quite involved, however since we are just doing localhost development and testing, we can bypass all the mumbo-jumbo and create the minimal unpassworded private key and SSL certificate the easy way. Do not use this method for creating production server SSL certificates
27 +Normally creating SSL certificates for production use is quite involved, however since we are just doing localhost development and testing, we can bypass all the mumbo-jumbo and create the minimal unpassworded private key and SSL certificate the easy way. Do not use this method for creating production server SSL certificates!
35 35  
36 -Open terminal and follow the commands shown below in my transcript which is self-explanatory if you are familiar with Terminal...
29 +* Open terminal and ...
37 37  
38 38  {{noformat}}
39 39  
40 -mymac$ cd /etc/apache2/
41 -mymac$ sudo -s
42 -
33 +$ cd /etc/apache2/
34 +$ sudo -s
35 +# mkdir devsslcerts
36 +# cd devsslcerts/
43 43  bash-3.2# mkdir devsslcerts
44 44  bash-3.2# cd devsslcerts/
45 -
46 -
47 -{{/noformat}}
48 -
49 -Next run the one single openssl command that will make the two files we need in their final folder that we just created above.
50 -Note you will be asked for a bunch of info for the certificate. Follow what I have done below. **In particular, enter "localhost" in the Common Name field**
51 -
52 -{{noformat}}
53 -
54 -bash-3.2# openssl req -days 3650 -new -x509 -nodes -out localhost_server.crt -keyout localhost_server.key
55 -
39 +bash-3.2# openssl req -new -x509 -nodes -out localhost_server.crt -keyout localhost_server.key
56 56  Generating a 1024 bit RSA private key
57 57  .........................++++++
58 58  .....++++++
... ... @@ -72,7 +72,6 @@
72 72  Organizational Unit Name (eg, section) []:Software Engineering Department
73 73  Common Name (eg, YOUR name) []:localhost
74 74  Email Address []:developer@webobjects.com
75 -
76 76  bash-3.2# ls -al
77 77  total 16
78 78  drwxr-xr-x 4 root wheel 136 Jul 21 16:58 .
... ... @@ -83,66 +83,6 @@
83 83  
84 84  {{/noformat}}
85 85  
86 -=== Configure Apache2 to Use Your Development Certificates for localhost ===
87 -
88 -Using your favorite command line editor, edit the apache config file at
89 -**/etc/apache2/httpd.conf**
90 -making the changes shown in the following 2 screenshots:
91 -
92 -{{panel title="Setting Apache server name to localhost"}}
93 -
94 -!step1_servernamelocalhost.jpg!
95 -
96 -{{/panel}}
97 -
98 -{{panel title="Including SSL Configuration file into main Apache config file"}}
99 -
100 -!step2_includesslconfig.jpg!
101 -
102 -{{/panel}}
103 -
104 -Next edit the ssl config file itself at
105 -**/etc/apache2/extra/httpd-ssl.conf**
106 -making the changes shown in the following sceenshot:
107 -
108 -{{panel title="Setting up the SSL Config file"}}
109 -
110 -!step3_sslconfig.jpg!
111 -
112 -{{/panel}}
113 -
114 -Restart apache
115 -
116 -{{noformat}}
117 -
118 -bash-3.2# apachectl graceful
119 -
120 -{{/noformat}}
121 -
122 -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
123 -
124 -JEFF SCHMITZ
125 -
126 -Right at this point I got the error:
127 -
128 -ulimit: open files: cannot modify limit: Invalid arg
129 -
130 -After a quick google search I found this which seems to have fixed the error:
131 -
132 -[[http://www.perkiset.org/forum/all_things_apple/apache_osx_and_ulimit_a_little_chunk_of_weirdness-t909.0.html]]
133 -
134 -Also, for my https:~/~/... links my rewrite rules in apache weren't getting fired.  To get them to work I had to add them to the httpd-ssl.conf file just below the General setup stuff shown in the figure above.  I just copied them from my httpd.conf file and pasted them in.  Not sure if this is the best way to handle it, but it's working for me on my development machine at least.
135 -
136 -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
137 -
138 -Finally, verify that https is working:
139 -
140 -{{panel title="Verify https://localhost is working"}}
141 -
142 -!httpslocalhost2.jpg!
143 -
144 -{{/panel}}
145 -
146 146  == Detecting SSL ==
147 147  
148 148  Code for detecting whether SSL is active for the current request: