Skip to Content
Last modified by Aaron Rosenzweig on 2012/03/19 19:33
From version 52.1
edited by Kieran Kelleher
on 2008/07/22 15:44
Change comment: There is no comment for this version
To version 54.1
edited by Pascal Robert
on 2012/01/27 09:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Web Applications-Development-SSL requests via https protocol
1 +Development-SSL requests via https protocol
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.kieran
1 +XWiki.probert
Content
... ... @@ -119,6 +119,22 @@
119 119  
120 120  {{/noformat}}
121 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 +
122 122  Finally, verify that https is working:
123 123  
124 124  {{panel title="Verify https://localhost is working"}}
... ... @@ -153,3 +153,37 @@
153 153  log.debug( "secure mode set to " + secureMode );
154 154  
155 155  {{/code}}
172 +
173 +== Using SSL in DirectConnect ==
174 +
175 +Mike Schrag said in early 2011 that it was possible to use SSL in DirectConnect, that is was simply hidden. A property was added to enable it, and instructions added to the Properties file of ERExtensions. This is the part from the Properties file:
176 +
177 +{{code}}
178 +
179 +
180 +## You should probably not enable any of these settings in a normal Apache webserver deployment,
181 +## in particular the ssl port property, as this is used by ERX to generate https URLs, which must
182 +## match your Apache config.
183 +##
184 +## To enable SSL support with DirectConnect, you must do the following:
185 +##
186 +## * In your Resources folder, run "keytool -genkey -alias WebObjects -keyalg RSA -keystore adaptorssl.key". Select a
187 +## password for your keystore (i.e. "changeit"), and set the "your first name and last name" field to match the hostname
188 +## that you will be running your directconnect app off of.
189 +## * In your Resources folder, create an executable script (it MUST BE EXECUTABLE) named "adaptorsslpassphrase" with the
190 +## contents:
191 +## echo changeit
192 +## where you should replace "changeit" for whatever password you selected in the previous step.
193 +## * Set the following property to true
194 +#er.extensions.ERXApplication.ssl.enabled=true
195 +
196 +## (optional) To specify an SSL host name other than what is returned from a call to
197 +## application.host(), you can override it below
198 +#er.extensions.ERXApplication.ssl.host=localhost
199 +
200 +## (optional) To select an SSL port other than 443, uncomment the following. If you are already running Apache with SSL,
201 +## you probably want to set this. If the port number is 0, the SSL port will be automatically assigned (using the same
202 +## mechanism that WO uses to set the regular port)
203 +#er.extensions.ERXApplication.ssl.port=0
204 +
205 +{{/code}}