Bug 56319 - Add Policy Kit textual agent listener to realm command
Summary: Add Policy Kit textual agent listener to realm command
Status: RESOLVED WONTFIX
Alias: None
Product: realmd
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Stef Walter
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-23 10:07 UTC by Stef Walter
Modified: 2015-04-11 11:26 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments
Register the 'realm' command as a fallback policy kit agent (4.14 KB, patch)
2012-10-30 15:08 UTC, Stef Walter 		Details | Splinter Review
View All

Description Stef Walter 2012-10-23 10:07:53 UTC 
Add Policy Kit textual agent listener to realm command, for running realm when no polkit agent is running, such as over ssh sessions.

See some more details here: https://bugzilla.redhat.com/show_bug.cgi?id=867807
Comment 1 Stef Walter 2012-10-30 15:08:56 UTC 
Created attachment 69318 [details] [review]
Register the 'realm' command as a fallback policy kit agent
Comment 2 Stef Walter 2012-10-30 15:11:34 UTC 
David, do you know why the attached patch doesn't work? The agent seems to register successfully in the 'realm' client process. But when I try to use this, I get back a NotAuthorized from the 'realmd' daemon.

Do the subjects have to match between the client and the daemon? In realmd we use a dbus system bus subject. I saw a ** WARNING ** when I tried to use that as the agent subject in the client:

** (realm:421): WARNING **: Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Only unix-process and unix-session subjects can be used for authentication agents.
Comment 3 Stef Walter 2015-04-11 11:26:50 UTC 
Lets not do this. Realistically, if you don't have polkit properly running (including an agent) then realmd only supports joining as root.

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.