Bug 2635 - SSO information can be outdated after reconnect
Summary: SSO information can be outdated after reconnect
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VSM Agent (show other bugs)
Version: trunk
Hardware: PC Linux
: P2 Enhancement
Target Milestone: LowPrio
Assignee: Peter Åstrand
Depends on:
Reported: 2008-01-18 11:29 CET by Erik Forsberg
Modified: 2022-05-31 12:59 CEST (History)
2 users (show)

See Also:
Acceptance Criteria:


Description Erik Forsberg cendio 2008-01-18 11:29:41 CET
We are currently not updating the SSO info at reconnect, which means that if a user has changed password since session was started, for example via ssh-keyboard-interactive in the ThinLinc client, SSO will not work as the stored password/pin/whatever is not updated. 

This will probably require a new XMLRPC call being implemented in VSM Agent where we tell the agent that a reconnect is about to happen. 

Another approach would be to have an XMLRPC call that only sets SSO info for the user, and call that after the session has been created, and at reconnect.
Comment 1 Henrik Andersson cendio 2016-05-02 12:49:49 CEST
This is also a problem when a user authenticates using different methods eg. smartcard vs. password. A typical scenario is using HTML5 client with password and reconnect using smartcard when using native client.

Note You need to log in before you can comment on or make changes to this bug.