Learn more about these different git repos.
Other Git URLs
This is a first part of providing account data for the Gnome account service and other customers.
As a first phase, we would write a new responder, that would provide a single method to get a custom attribute. Further care must be taken to ensure that only certain attributes might be read by certain consumers (polkit? tbd).
This code would be marked as experimental in upstream so that we could consider the API unstable and change it at will.
milestone: NEEDS_TRIAGE => SSSD 1.12 beta
priority: major => critical
rhbz: => todo
Jakub, have you had a chance to do a patch or branch here? I know there's been a lot going on, but figured I'd check in case I missed something.
Not much except for the finished POC for Jan P and a follow up discussion with Simo on the team list. Unfortunately RHEL-7 has been demanding most of the time so far. We're about to release 1.11.1 (today hopefully..) which means I will have more time when that one is out. Sorry.
The POC for Jan is here:
OK, RHEL-7 fires have been put off and I can finally start on this work.
owner: somebody => jhrozek
status: new => assigned
summary: Provide an experimental DBus responder to retrieve custom attributes from SSSD cache => [RFE] Provide an experimental DBus responder to retrieve custom attributes from SSSD cache
The responder itself was rebased on Stef's code and pushed to master:
Since the ifp responder is in master, I'm closing this ticket. We are tracking the other subtasks such as getsetters, ObjectManager support or object caching in separate tickets.
resolution: => fixed
status: assigned => closed
design: => https://fedorahosted.org/sssd/wiki/DesignDocs/DBusResponder
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1115475
rhbz: todo => [https://bugzilla.redhat.com/show_bug.cgi?id=1115475 1115475]
Metadata Update from @jhrozek:
- Issue assigned to jhrozek
- Issue marked as depending on: #2227
- Issue set to the milestone: SSSD 1.12 beta
SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here:
If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.
Thank you for understanding. We apologize for all inconvenience.
to comment on this ticket.