Skip to main content

Delegation mailbox through EWS managed API 2.0

Goal to create NETIQ Identity Manager Driver integeration for Microsoft Exchange using EWS(Exchange Web Services) managed API 2.0
the error:
'The specified object was not found in the store.'

finally things are working fine when i poll the exchange mailbox for a specified user in the single forest single domain environment, but situation i came across was to read a resource mailbox using a different user account creds home in different AD forest using EWS..

So it was all about Delegation.. well the environment i was working was little bit different then things usually seems to be happen in dreams and in books/documentation world..  the Exchange was hosted as a "Accoutn/Resource" forest deployment fashion, that mean my user account was homed in a different forest then the Exchange resource mailbox.

they way  i worked it out was by applying a powershell on the exchange mailbox such as:

Add-MailboxPermission -Identity 'CN=testMailbox,OU=Test,DC=ad,DC=resource,DC=com' -User 'Account\maqsood' -AccessRights 'FullAccess'

I could not find the EMC(Exchange Management Console)  much of help to add the user from different Account forest from within Managed Full Access Permission option.

Then i changed my code FROM_


Folder rootfolder = Folder.Bind(service, WellKnownFolderName.Inbox);
     rootfolder.Load();

TO_


 Folder rootfolder = Folder.Bind(service, new FolderId(WellKnownFolderName.Inbox, ConfigurationManager.AppSettings.Get("ResourcePrimaryEmailAddress").ToString()));  
       


any yes, things much better!..

and now its time to tear up the test!

Comments

Post a Comment

Popular posts from this blog

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

NetIQ IDM - JDBC driver - SQL calls from driver (Publisher channel) using XSLT

Recently I was working on a task where we had to call some SQL statements from publisher channel on a JDBC driver to different tables than the ones driver was configured to sync. The official documentation suggest to achieve this using jdbc-statement but it only schedules them on the subscriber channel, best suited for calling some SQL for stored procedure. The way I solved it was using XSLT and enabling Subscriber channel. On the publisher  Command Transformation Channel , I have following XSLT: < xsl:stylesheet xmlns:xsl = "http://www.w3.org/1999/XSL/Transform" xmlns:jdbc = "urn:dirxml:jdbc" xmlns:query = "http://www.novell.com/nxsl/java/com.novell.nds.dirxml.driver.XdsQueryProcessor" version = "1.0" > < xsl:param name = "srcQueryProcessor" /> < xsl:param name = "destQueryProcessor" /> < xsl:template match = "node()|@*" > < xsl:copy > &
Post a Comment
Read more