MJ J wrote:
> Service accounts typically use the simpleSecurityObject object class.
But one needs an appropriate structural object class to add the entry.
'simpleSecurityObject' is an auxiliary object class without any naming
attribute.
Ciao, Michael.
> On Tue, Dec 19, 2017 at 9:15 PM, Douglas
Douglas Duckworth wrote:
> It seems I created this service account with posixAccount objectClass.
> That requires uidNumber.
>
> So I need to do some research on what's the appropriate objectClass for
> this service account. It's used by SSSD and Apache, for example, to
> perform binds with our
Service accounts typically use the simpleSecurityObject object class.
On Tue, Dec 19, 2017 at 9:15 PM, Douglas Duckworth
wrote:
> It seems I created this service account with posixAccount objectClass. That
> requires uidNumber.
>
> So I need to do some research on
It seems I created this service account with posixAccount objectClass.
That requires uidNumber.
So I need to do some research on what's the appropriate objectClass for
this service account. It's used by SSSD and Apache, for example, to
perform binds with our LDAP cluster since we do not allow
Michael Ströder wrote:
After so many years passing around parameter clientctrls (e.g. in a
wrapper module) I'm still wondering which use-cases this argument is
meant for.
I only found [1] but this seems akward today anyway.
Agreed, OID-based controls for client-side library behavior seems