Bug 49085 - support username for authentication
Summary: support username for authentication
Status: RESOLVED WONTFIX
Alias: None
Product: Spice
Classification: Unclassified
Component: protocol (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Spice Bug List
QA Contact:
URL:
Whiteboard:
Keywords:
: 39070 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-04-23 11:19 UTC by David Jaša
Modified: 2012-11-21 17:45 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description David Jaša 2012-04-23 11:19:12 UTC
While username is not necessary for any Spice-based product now, it would be useful for some possible future uses like remote access to server management consoles so spice protocol could incorporate it for such cases. Virt-viewer already can ask for username if needed so the only server-side changes would be needed to have this implemented fully and they can be postponed to the time when sombody wants to leverage it.
Comment 1 Marc-Andre Lureau 2012-04-23 12:38:24 UTC
(In reply to comment #0)
> While username is not necessary for any Spice-based product now, it would be
> useful for some possible future uses like remote access to server management
> consoles so spice protocol could incorporate it for such cases. Virt-viewer
> already can ask for username if needed so the only server-side changes would be
> needed to have this implemented fully and they can be postponed to the time
> when sombody wants to leverage it.

That doesn't really fit with Spice atm. Unless we have a clear plan on how we want to dispatch a connexion to different servers/session, it doesn't quite work.

I believe VNC being implemented at a higher level was able to have services/proxy to redirect a connexion to a particular session. But Spice isn't at this level.
Comment 2 Will Thompson 2012-11-21 17:45:45 UTC
*** Bug 39070 has been marked as a duplicate of this bug. ***


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.