[sssd PR#5262][opened] Dn with spaces
by elkoniu
URL: https://github.com/SSSD/sssd/pull/5262
Author: elkoniu
Title: #5262: Dn with spaces
Action: opened
PR body:
"""
This PR is push to upstream work of @thalman as he is on PTO now.
Those 2 commits fixes issue with white space in DN reported by one of clients.
Client already confirmed that this solves the issue for him. When @thalman will be back from PTO he will took over this.
"""
To pull the PR as Git branch:
git remote add ghsssd https://github.com/SSSD/sssd
git fetch ghsssd pull/5262/head:pr5262
git checkout pr5262
3 years, 6 months
[sssd PR#5306][opened] sss_cache: sss_cache exits immediately if SSSD is not running.
by tomofumi-yoshida
URL: https://github.com/SSSD/sssd/pull/5306
Author: tomofumi-yoshida
Title: #5306: sss_cache: sss_cache exits immediately if SSSD is not running.
Action: opened
PR body:
"""
When running sss_cache if /var is mounted as NFS,
the fcntl access time to /var/lib/sss/db/timestamps_implicit_files.ldb is accumulated
and the sss_ cache command took a long time to complete.
Not only executing sss_cache directly, but also sss_cache may be executed
by other commands (for example, useradd and groupadd in shadow utility).
In this case, I encountered this problem when running useradd.
It is hard for all callers of sss_cache to fix,
so fix sss_cache to exit immediately while SSSD is not running.
"""
To pull the PR as Git branch:
git remote add ghsssd https://github.com/SSSD/sssd
git fetch ghsssd pull/5306/head:pr5306
git checkout pr5306
3 years, 6 months
[sssd PR#5344][opened] be: remove accidental sleep
by pbrezina
URL: https://github.com/SSSD/sssd/pull/5344
Author: pbrezina
Title: #5344: be: remove accidental sleep
Action: opened
PR body:
"""
This sleep was used to test a crash in data provider and quite unfortunately
it was left in the patch.
dp: fix potential race condition in provider's sbus server
4a84f8e18ea5604ac7e69849dee492718fd96296.
Perhaps this is the cause of recent failures in session recording tests.
"""
To pull the PR as Git branch:
git remote add ghsssd https://github.com/SSSD/sssd
git fetch ghsssd pull/5344/head:pr5344
git checkout pr5344
3 years, 6 months
Re: Implementing an AAD plugin
by Sumit Bose
On Wed, Sep 30, 2020 at 08:54:57PM +0000, Yancho Yanev wrote:
>Hello,
>
>We are trying to integrate Azure Active Directory with Linux. We already did NSSWITCH and PAM prototypes but it looks like SSSD is a much better extension place because of the caching and offline capabilities.
>Unfortunately I cannot find sample code or instructions how to write a SSSD plugin. Neither I can see a devel package with the interface definitions.
Hi,
thank you for reaching out to us, this sound like a very interesting
project.
I think the best way to understand how to add a new backend is to look
at existing code. It is expected that a new backend is implemented in
the SSSD tree hence there is no devel package for backends.
>
>How do we add a provider? Can we do it in our own repo or the only way is to develop in yours?
>Also, I see that you are "fedorahosted". If this a clone for Fedora only? Does your enlistment produce Ubuntu packages or is the Ubuntu stuff in a different place?
"fedorahosted" was one of the first hosting platforms we used, but the
current development happens on github https://github.com/SSSD/sssd which
we use for bug reports and pull request as well. This project is not
Fedora specific the SSSD Ubuntu, Debian, SuSE etc packages are build
from this source as well.
How different is "Azure Archive Directory" from classical "Active
Directory"? Would it make sense to enhance the existing SSSD AD provider
or would it make more sense to create a new one?
At simple example for a backend is
https://github.com/SSSD/sssd/tree/master/src/providers/simple which only
implements an access_provider which corresponds to the functionality you
might have already implemented in pam_sm_acct_mgmt() in you PAM
prototype.
The main parts of backend interface are an init function e.g.
https://github.com/SSSD/sssd/blob/master/src/providers/simple/simple_acce...
with a name like sssm_BACKENDNAME_FUNCTIONTYPE_init. This init function
should call dp_set_methods()
https://github.com/SSSD/sssd/blob/master/src/providers/simple/simple_acce...
to specify the function which should be called to process the request.
For a start you need init functions for user and group lookups
corresponding to what you have in the NSSWITCH prototype (e.g.
https://github.com/SSSD/sssd/blob/master/src/providers/ad/ad_init.c#L520),
for authentication (pam_sm_authenticate) (e.g.
https://github.com/SSSD/sssd/blob/master/src/providers/ad/ad_init.c#L546)
and access control (e.g.
https://github.com/SSSD/sssd/blob/master/src/providers/ad/ad_init.c#L572).
Do you have your prototypes accessible in a public repo? If yes, I'd be
happy to check what would be the most easy start to add this to SSSD.
For a prove of concept you might even consider to use your prototypes
with SSSD's proxy provider which can load existing nss and PAM modules,
see man sssd.conf for details. But this would be only for a very first
start.
Please do not hesitate to ask further questions here or by sending an
email directly to me.
HTH
bye,
Sumit
>
>Thank you,
>Yancho Yanev
>_______________________________________________
>sssd-devel mailing list -- sssd-devel(a)lists.fedorahosted.org
>To unsubscribe send an email to sssd-devel-leave(a)lists.fedorahosted.org
>Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>List Archives: https://lists.fedorahosted.org/archives/list/sssd-devel@lists.fedorahoste...
3 years, 6 months