[wpkg-users] [Bug 208] domain group is not correctly retrieved
bugzilla-daemon at bugzilla.wpkg.org
bugzilla-daemon at bugzilla.wpkg.org
Fri Nov 18 00:26:05 CET 2011
http://bugzilla.wpkg.org/show_bug.cgi?id=208
Rainer Meier <r.meier at wpkg.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |WORKSFORME
--- Comment #8 from Rainer Meier <r.meier at wpkg.org> ---
I have tried to find a better way using WMI queries like "ASSOCIATORS OF
{Win32_UserAccount.Domain='<domain>',Name='<host>$'} WHERE resultClass =
Win32_Group" in order to find all groups the host is associated to. Without any
success yet.
Unfortunately the code provided is unusable for WPKG as it requires the groups
to be known. I have checked whether the groups attribute content could be used
(I think this is what you suggested) but this is not suitable for WPKG as WPKG
requires to query the full list of group membership in order to store this list
in the local settings file for remote query feature. Fetching potential groups
from conditions is therefore not an option.
I regard this as a limitation of WSH. So WPKG will only support to matching of
native Windows NT group.
Note that you might always use external tools to do LDAP queries or whatever
you like by using an type="execute" check to run an external tool/script.
Stefan might be able to provide such a tool which checks group membership using
LDAP queries. This approach allows extending the condition functionality with
any external script without having to mess with WPKG internals with potential
disadvantages for other users (like slow/delayed execution due to group queries
which are used by a minority of users only).
Setting to "resolved" again as the current implementation works as designed.
Admittedly some users would like extended matching but WPKG already supports
this by execute type checks.
--
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the wpkg-users
mailing list