I've been implementing a CWI project against a server with basic authentication through Apache. I use a Credentials Statement with a onTransactionStarted handler to supply the connector with credentials from the user (variables to the transaction).

The trouble is, after the first login, the Convertigo server seems to remember this login for ALL clients! Even if I restart the Convertigo web app they are remembered. Only when I restart tomcat are they forgotten.

Oups, this is clearly a bug...

Perhaps so! I thought maybe there was something I was missing.

After looking at this a bit more, I think there may be a problem in my projects causing this. I think this because when I enter incorrect credentials on a subsequent connection, I see the error screen being processed by Convertigo.

Unfortunately I am not able to look into this further right now, but I thought I'd let anyone know who read this that it was possibly a problem with my implementation and not a bug in Convertigo.

I think that I have resolved this for the most part. Unfortunately (for me), it was all errors from me.

My target system has some complex authentication. I needed to look at the process through firebug to see where the frontpage was redirecting to before anything else. I changed my login transaction to point there and things began to smooth out immediately.

I've also been confused about the "Maintains connector state" property of my transactions. I'm not sure exactly what this means, but using it was causing more confusing behavior for me. Combined with the use of a Sequencer connector, I've change to provide the credentials with each request, simply because I can't be sure which transaction will be fired by the user first.

It's not a clear explanation of what went wrong, but I am reassured that Convertigo is quite able to handle authentications like this.

I've also been confused about the "Maintains connector state" property of my transactions.


When launched, "Maintains connector state = false", aka "stateless" transactions re-establish a fresh connection on their target URL.
Note that related cookies are cleaned in the process.

"Maintains connector state = true", aka "statefull" transactions do not connect. Instead, they take the connector in its present state, and go on from there.

So, although there are exceptions, a chain of transactions is often made by a stateless transaction followed by statefull transactions.