CSAM multiple connection on Chromium keep data of the first user

[Léopold Van Beirs]

Hello, 

I am in the process of setting up a digital kiosk. Our kiosk allows you to identify yourself via CSAM with your ID card, but after the first user logs out, we can't identify a second user. Our kiosk software runs on Windows and uses a Chromium browser. I've tried several solutions: 1. delete the certificates in the Windows Certificate Store. 2. Empty the browser cache. The only "solution" that works is to restart the browser ... but in the case of a digital kiosk this isn't very "user friendly".
Do you know of a solution for identifying several users at once under Chromium?
Maybe with a Chrome flag?
Deleting a specific partition?
By restarting the eID middleware?

[Frederik Vernelen]

Hello Leopold, 

Restarting the middleware will not solve your issue, it is just a component in between your browser and smart card (reader) that facilitate the communication, but it does not cache anything from previous connections.

What might be worth looking at is how you log out the previous user from the https connection. (make sure that the TLS session gets terminated, if the browser tries to re-use/continue the previous client session, you run into the situation you describe)

I assume that the initial user is capable of logging in again? (probably continuing/refreshing the tls session).

Wkr,

 Frederik

--
You received this message because you are subscribed to the Google Groups "eID Middleware Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eid-middleware-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/eid-middleware-dev/e18dc063-4b4f-4da6-acc0-c95deb60806fn%40googlegroups.com.

[Léopold Van Beirs]

Hi Frederik,

Thanks for the quick and detailed reply.

"I assume that the initial user is capable of logging in again? (probably continuing/refreshing the tls session)"

Yes, this is correct !

I will take a look into the logout logic and check the TLS session status.

But do you know a way to properly close/terminate the TLS session after logout or manually from the browser ?

Maybe CSAM has a dedicated logout URL or can we perform this action from Chrome directly ?

Kr,

Léopold Van Beirs