Highlighted
fp_idmworks Super Contributor.
Super Contributor.
534 views

Dynamic Group Query


IDM 4.5.1


I may have my policy incorrect, but wondering if someone would be
willing to give it a peak to see if the logic is right.

I have tried using Member and [psuedo].Member with no success on
either.

I'm getting a 610 error but my traces don't show values for the local
variables and assuming it is a 610 as the local variables are null or
have no value.



<do-set-local-variable name="lv_TermUsers" scope="policy">
<arg-node-set>
<token-query class-name="Group" datastore="src" scope="entry">
<arg-dn>
<token-global-variable name="gcv_TermUserGroupUS"/>
</arg-dn>
<arg-match-attr name="Member"/>
<arg-string>
<token-text xml:space="preserve">Member</token-text>
</arg-string>
</token-query>
</arg-node-set>
</do-set-local-variable>

Thanks,
Fred


--
fp_IDMWORKS
------------------------------------------------------------------------
fp_IDMWORKS's Profile: https://forums.netiq.com/member.php?userid=9869
View this thread: https://forums.netiq.com/showthread.php?t=54524

Labels (1)
0 Likes
4 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Dynamic Group Query

As always, a trace, particularly including the driver startup, may be
helpful to verify the GCV values.

It looks like you're trying to set a local variable to the result of a
query to the source for a Member attribute, so I presume this is meant to
fire on a Group (vs. User) object. What I cannot figure out is what the
<arg-match/> portion is doing in there. If you are querying for an entry,
why have a matching attribute as well, and if you want Member back, why
use Member as a matching argument?

Knowing what this does, and when, along with the trace, would probably
help make this clearer to us.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Knowledge Partner
Knowledge Partner

Re: Dynamic Group Query


Hi Fred,
It is also not clear for me what exactly you tried to achieve.
You take "member" information from your current object (group)
(potentially this is nodeset of users dn), make query to the group
*gcv_TermUserGroupUS* with matching criteria nodeset of members of your
current object (group).
I'm not sure, if query token will be able to make this kind of
matching.

Alex


--
If you find this post helpful, please show your appreciation by clicking
on the star below :cool:
------------------------------------------------------------------------
al_b's Profile: https://forums.netiq.com/member.php?userid=209
View this thread: https://forums.netiq.com/showthread.php?t=54524

0 Likes
fp_idmworks Super Contributor.
Super Contributor.

Re: Dynamic Group Query


Thanks for the replies. You are right Aaron, matching shouldn't be used
in this scenario. I was trying a various set of combinations with the
query in hopes of finding where I went wrong.

My DN on my GCV was incorrect and I was getting a 9010 and -610 error.
Once I put it in slash format the error went away. I was able to use the
[psuedo].Member to pull the members.

thanks,
Fred


--
fp_IDMWORKS
------------------------------------------------------------------------
fp_IDMWORKS's Profile: https://forums.netiq.com/member.php?userid=9869
View this thread: https://forums.netiq.com/showthread.php?t=54524

lkr Contributor.
Contributor.

Re: Dynamic Group Query

Hey Fred,

This post is useful to me.

I am also trying to query all the members inside one of the Dynamic Group.

I am using the below query based on your recommendations still I am getting the empty value

<do-set-local-variable name="Getinfo" scope="policy">
<arg-string>
<token-query datastore="src" max-result-count="10" scope="entry">
<arg-dn>
IDMDEV\corp\groups\TermUsers
</arg-dn>
<arg-string>
[psuedo].Member
</arg-string>
</token-query>
</arg-string>
</do-set-local-variable>

 

Thanks,

Lucky.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.