Convio Donation API leaving session cookie bound to a constituent - how do you remove this?

Options

We have a custom application using the Convio donation API. In this application, a single user may donate multiple times. However, in our data model, each of these donations may be for a different constituent record (even though they were made by the same user). We are providing Convio with the correct email address of that constituent. However, the donation API ends up using the first constituent that was used during the first donation for that browser session. A quick look at the cookies set in my browser during the donation shows that secure2.convio.net created a session cookie during the donation. Since I can't remove this cookie with my application, is there any other way to effectively "log a user out" after a donation was made via the donation API? We don't want that browsers session to continue to have any relationship with a constituent record!

I tried the logout API method but the cookies still remained after calling it.

Any help would be appreciated!

Tagged:

Comments

  • I'm having a similar problem with a cookie being left by the server Constituent>createorupdate method. I'm making the call from a Flash file, and I call the logout API method afterwards. But, there is still a cookie for the API user I'm using to authenticate. Is there any way to remove the cookie? Any help is greatly appreciated!

  • The logout API actually did end up solving our problem. I believe a cookie from Convio did still remain on the session, but if you use the loginTest API after calling the logout API, you will notice that no constituent is logged in on the web browsers session. For the loginTest method, we just put the URL in the web browser - Firefox rendered the result in the XML response so we were able to validate that the browsers session no longer had the cookie on it.

Categories