I'm still working on the enumeration support, but I wanted to get the
direct lookup on the list early.
Patch 0001: extend sysdb_store_service() to accept additional attributes
This is necessary to be able to store provider-specific data in the
entry (such as the entryUSN).
Patch 0002: Add a helper function to get an integer value from a
sysdb_attrs object directly as a uint16_t.
Patch 0003: The big one. This patch adds support for looking up services
in LDAP. There shouldn't be any big "gotchas" here. It's very
straightforward (if long).
Patch 0004: Extend this support to the IPA Provider (even though IPA
itself does not yet support the services map natively).
We have many AD groups that don't have valid characters in them as far as Unix group names are concerned. We'd like to use these AD groups in Unix land without having to rename. In the past we have defined a character mapping to fix the invalid characters, so use an altered name in Unix land. The most important thing is the membership of the groups which is properly maintained in Windows land. I was hoping to use the same character mapping and put the translated name into a spare Attribute of the AD group. The one that looks suitable is msSFU30Name but trying this does not seem to work.
I am testing by putting this line in my sssd.conf file
ldap_group_name = msSFU30Name
For groups with this Attribute set, the id command shows the gid (gidNumber set in AD) of the group but no group name. For those groups without a value in msSFU30Name I see the AD group name as well as the gid. For those groups with invalid characters in the name I see no mention at all in the id command output.
I guess I have 2 questions - 1. Should this work? 2. If it won't work are there any other suggestions to solve the group name character set problem.
Hi - We're using SSSD with LDAPS and TLS on redhat, and it's working
fine. I just tried to make it work for unbuntu, but I can't get TLS to
work. I get the following errors:
(Mon Jan 30 14:36:09 2012) [sssd[be[PSFC]]]
[sss_ldap_init_sys_connect_done] (1): ldap_install_tls failed: Connect error
(Mon Jan 30 14:36:09 2012) [sssd[be[PSFC]]] [sdap_sys_connect_done] (1):
sdap_async_connect_call request failed.
if I disable TLS, it works ok. I verified that the certificates are
valid using the openssl verify command. Any other suggestions? I
would be willing to build the latest version of SSSD for Ubuntu, to see
if that would help. Unfortunately, I can't find the correct parameters
for the ./configure command, to build it on Ubuntu. Can anyone point me
to that? Thanks. - Mark
[PATCH 1/2] HBAC docs: Fix path to libipa_hbac header file
I noticed the HBAC docs directory contained just a stub index.html
[PATCH 2/2] SUDO: Provide documentation for the SUDO API
The API should be documented in order to be easily consumable by the
The glibc headers probably changed between recent Fedora releases and
RHEL5 resulting in compilation errors on RHEL5 when building with sudo
The attached patch adds two missing includes in the sudo code and one in
the sss client that was triggered by adding sudo support.
please could you give some reference about the functionality provided by
the sssd.api.conf file?
I'm searching on the net but not finding any documentation. Is it a file
that need to be managed manually or not?
Any guidance appreciated.
Thanks in advance
Non è forte chi non cade, ma chi cadendo ha la forza di rialzarsi.