Author |
Message |
29/06/2015 15:13:27
|
brandt
Power User
Joined: 12/03/2008 16:37:34
Messages: 45
Location: Bern
Offline
|
Hi community,
does anyone of you have experience in starting a CaptainCasa application via JavaWebStart with a proxy server for authentication running in front of your application server?
Our scenario is as follows:
The user has to logon on a webpage in the browser. After a succesfull login he is directed to the next webpage. This webpage contains a link to a jnlp-file to start our application. My hope was that the cookie of the browser session was automatically shared with the JavaWebStart process. But unfortunately the browser session cookie was not used by JavaWebStart. And our proxy server answers all requests from JavaWebStart with "Authentication required".
Has anyone of you solved this problem?
Any help or hint is welcome.
Regards
Joe
|
|
|
06/07/2015 07:16:27
|
CaptainCasa
Power User
Joined: 21/11/2007 12:23:06
Messages: 5528
Offline
|
...we had some phone conversation on this, so the result is:
According to http://docs.oracle.com/javase/7/docs/technotes/guides/jweb/decision_guide.html only persistent cookies are "transferred" from browser to web start - not transient session-cookies.
Solution is:
*.jar libraries have to be stored in some public area so that web start can load them.
CaptainCasa will provide some mechanism to transfer cookies from the calling link (JNLP / .ccwebstart) into the http(s)-communication of the Swing/FX-Client.
Regards, Björn
|
Björn Müller, CaptainCasa GmbH |
|
|
03/08/2015 08:35:56
|
brandt
Power User
Joined: 12/03/2008 16:37:34
Messages: 45
Location: Bern
Offline
|
Hi Björn,
only one short question.
Is the mechanism to set the cookie already implemented?
I could not find an according entry in the change log.
Regards, Joe
|
|
|
03/08/2015 08:49:14
|
CaptainCasa
Power User
Joined: 21/11/2007 12:23:06
Messages: 5528
Offline
|
....yes, it is.
In the URL ".....xyz.ccwebstart" or ".....xyz.ccapplet" (same with FX variants) you can pass parameter "?cctransfercookies=true" (or "?a=b&c=d&cctransfercookies=true" if there are already query parameters).
In this case the cookie values are internally added as client parameters "http-cookie:<cookiename>=<cookievalue>" into the calling of the CC client.
The CC client itself now knows about the cookies and during communication adds all cookies unter their orignal name (without "http-cookie:") into the requests that it sends to the server side.
So the result:
All cookies that are part of the .ccapplet/.ccwebstart request are afterwards part of the CC-Client-requests.
Regards, Björn
|
Björn Müller, CaptainCasa GmbH |
|
|
03/08/2015 08:57:35
|
brandt
Power User
Joined: 12/03/2008 16:37:34
Messages: 45
Location: Bern
Offline
|
Hi Björn,
perfect. Thank you very much.
Regards, Joe
|
|
|
|