Skip to main content

Reading Component type attribute values such Email Address





Read Email Attribute from Group:

<do-set-local-variable name="local.sub.etp.MailboxEmail" scope="policy"> <arg-node-set> <token-src-attr class-name="Group" name="EMail Address"> <arg-dn> <token-local-variable name="loca.sub.etp.Group"/> </arg-dn> </token-src-attr> </arg-node-set> </do-set-local-variable>



This would do following Output:


<nds dtdversion="4.0" ndsversion="8.x"> <source> <product edition="Advanced" version="4.5.6.0">DirXML</product> <contact>NetIQ Corporation</contact> </source> <output> <instance class-name="Group" qualified-src-dn="/N/A" src-dn="/N/A" src-entry-id="1026028"> <attr attr-name="EMail Address"> <value timestamp="1517759042#70" type="structured"> <component name="eMailType">3</component> <component name="eMailAddr">na@noname.com</component> </value> </attr> </instance> <status level="success"></status> </output> </nds>


Do Xpath to read the eMailAddr part from it:

<do-set-local-variable name="SingleEmailAddress" scope="policy"> <arg-string> <token-xpath expression="$local.sub.etp.MailboxEmail/component[@name='eMailAddr']"/> </arg-string> </do-set-local-variable>

Comments

Post a Comment

Popular posts from this blog

NetIQ IDM - JDBC statemens using policy builder

Few examples of using JDBC statements using dirxml policies On the Output policy: Handling matching policies with operation-data support: < rule > < description > [DB] Convert Query to DDL doc </ description > < comment name = "author" xml:space = "preserve" > Maqsood Ali Bhatti </ comment > < comment name = "version" xml:space = "preserve" > 5 </ comment > < comment name = "lastchanged" xml:space = "preserve" > Dec 20, 2017 </ comment > < conditions > < and > < if-operation mode = "case" op = "equal" > query </ if-operation > </ and > </ conditions > < actions > < do-append-xml-element expression = ".." name = "jdbc:statement" /> < do-append-xml-element expression = "../jdbc:statement[las...
Post a Comment
Read more

NetIQ IDM - Strip unwanted group member values from current operation

This code example shows how to remove unwanted group members from current operation based on some business logic. Optimization group members add to avoid  "ALREADY_EXIST_VALUE" kind of errors. when IDM engine fails to do so. Here I am doing look up in AD for members, and for each added member from IDM if user is already member of AD group, i am just striping out current member value from the current operaiton. < do-set-local-variable name = "group-dn" scope = "policy" > < arg-string > < token-src-dn /> </ arg-string > </ do-set-local-variable > < do-set-local-variable name = "group-members" scope = "policy" > < arg-node-set > < token-dest-attr class-name = "Group" name = "Member" /> </ arg-node-set > </ do-set-local-variable > < do-trace-message > < arg-string ...
Post a Comment
Read more

NetIQ IDM - Adding operation-data to subscriber command transformaiton custom commands

Recently i had to execute EOL cmdlets using psexecute though new NetIQ azure ad driver, since this operation is fire and forget in nature, i would like to track whole request and response for my own generated commands from subscriber command transofrmaiton policy, so i solved it by following policy: < do-set-dest-attr-value direct = "true" name = "psexecute" > < arg-association > < token-resolve datastore = "src" > < arg-dn > < token-text xml:space = "preserve" > {userref} </ token-text > </ arg-dn > </ token-resolve > </ arg-association > < arg-value type = "string" > < token-local-variable name = "cmdlet" /> </ arg-value > </ do-set-dest-attr-value > < do-append-xml-element expression = "../modify[@direct]" na...
2 comments
Read more