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 - 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 - SOAP driver -- Handling SOAP service response and manufacturing user association without XSLT

Always pain working with SOAP service and its handling of service response on Query(matching) for user to work with matching policies? Here is the quick wins; without reading  those long lengthy & boring useless SOAP driver blog series at netIQ forums; 1. Make sure you have mapped User class in the schema map with some service attributes 2. Make sure Input and Output policy is registered with all the namespaces you have in your request/response soap messages, example <policy xmlns:soap="http://www.w3.org/2003/05/soap-envelope" 3. I have added operation-data (which is being generated from the Output policy) as part of the SOAP query, but you can skip it if you do not need this. src-dn and association are important to indicate engine for building association.  Operation data will help you to identify operation type and you can carry actions according to it. Inject this on Output ( To support user matching) to send service request: < rule > ...
1 comment
Read more