How to disable multiple connections?

0

I believe when SAML is used with appstream a user is limited to a single connection. If they log-in a second time while a previous connection is open the previous connection is disconnected. Is there any way to get this behavior (concurrent connections limited to 1 ) when embedding create-streaming-urls? When embedding create-streaming-urls the previous connection seems to remain open. I don't see any parameters that would facilitate this on the the create-streaming-url api method nor is there something like expire-connections.

Thanks, Jonah

已提问 6 个月前288 查看次数
1 回答
1

AppStream sessions are not re-used or forcibly taken over should a user log in a second time. A new session is established on a new instance and old session still remains, as you indicated.

For a user to change devices/browsers/locations and retain the current session, they would need to disconnect first and reconnect within the specified timeout period (admin-configurable) to connect to the same session and continue, you can also try to expire a session using AWS CLI command: expire-session to expire a previous session.

AWS
已回答 6 个月前
  • Yea the expire-session command is a bit to heavyweight as it destroys the instance. I might look into seeing if I can have my app call DCV to disconnect the other connection although the sequence of events won't be ideal there. I'll have to have some sort of service though as DCV commands need admin privileges.

  • Well I implemented this so that dcv close-connection gets called prior to handing out a new createStreamingUrl but unfortunately the existing client immediately tries to reconnect and succeeds.

  • We were able to use the disconnect event to disable the auto-reconnect. We coupled this with a service do this selectively and only allow the most recent connection to reconnect.

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则

相关内容