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

Experience writing a Java based DirXML Driver

Based on the customer project, I wrote a DirXML driver which provision users through Novell Identity Manager 3.5.1 to their company intranet portal ( A Plone System). The portal exposed the RESTful API interfaces. So I started looking first at the Novell SOAP driver to see if it fit our needs. But while reading the driver documentation i felt it required too much XSLT knowledge + more customization and testing on the driver. And again it used the Apache HttpClient, Which is more a HttpClient rather then it targets to any specific protocol implementation. So If you could build SOAP messages at your own so it would help you in transporting these message back and forth between IDM and Application. The Novell SOAP driver comes up with two built in configurations "SPML and DSML", but in my case none of them were suitable. I had always wished to write my own DirXML driver at my own, so I thought why not just take this opportunity to fulfill my wish and at the same time get s...
1 comment
Read more

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

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 = "1...
Post a Comment
Read more