| Summary: | Add Policy Kit textual agent listener to realm command | ||
|---|---|---|---|
| Product: | realmd | Reporter: | Stef Walter <stefw> |
| Component: | General | Assignee: | Stef Walter <stefw> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | CC: | stefw, zeuthen |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | Register the 'realm' command as a fallback policy kit agent | ||
|
Description
Stef Walter
2012-10-23 10:07:53 UTC
Created attachment 69318 [details] [review] Register the 'realm' command as a fallback policy kit agent 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. 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.