Enterprise Client Community

I want to describe my experience with captain casa and single sign on. The requirement was to connect our captain casa base application with one of our customer existing reverse proxy single sign on infrastructure. Without any customization we got a HTTP 401 error during the start of our application. Apparently the single sign on memorized the authenticated connection using cookies and with the support of Mr. Mueller we figured out that a special parameter is required in the applet configuration:

<param name="sendcookies" value="true">

Using this parameter captain casa keeps the cookies of the connection. This is the connection where the browser puts the authorisation cookie after communication with the reverse proxy.

Unfortunately it’s not possible yet to keep only specific cookies. So it’s possible to keep unwanted cookies too. But we are looking forward to a captain casa update which provides the possibility to keep only cookies with defined names