Share all details about your problem, including any error messages you may have received.
Hi Everyone,
Currently , I am working on managing exchange online attributes from SailPoint IdentityIQ and I need your help to check if few attributes can be aggregated / updated /managed from external sources via Microsoft Graph API / Azure AD Connector.
We have Azure AD connector setup and in order to manage exchange online we are using certificate based authentication. We are able to preview the EXO_<Attributes> when updated in the account schema.
Use Case : Set the Retention Policy and Disable Mobile (Exchange Active Sync) for the newly created users in exchange online from SailPoint IdentityIQ.
SailPoint IdentityIQ now connects to exchange online using certificate based (App only) authentication mechanism. IdentityIQ connector will be able to manage the exchange online attributes if we update the appropriate attribute name with the format EXO_<AttributeName> under SailPoint application account schema as shown below. I can figure out the attribute for RetentionPolicy and when added under account schema we can see the values for the user accounts.
The issue here is that we are unable to figure out the appropriate attribute name for Mobile(Exchange Active Sync) .
The below power shell script is executed to disable the active sync for use.
But when I add EXO_ under schema , it says invalid property in the IQ Service logs (which means incorrect attribute). I have tried many attribute names, but nothing works. Here are the few combinations.
I believe the PowerShell command you’re using is correct for enabling or disabling ActiveSync. While provisioning shared mailbox attributes often requires the EXO prefix, I don’t think that’s applicable in this case for managing these specific attributes.
Hi Sunny, thanks for the reply. We have opened a sailpoint case and they confirmed that Azure Active Directory connector currently does not support managing the attribute mobile active sync. I need to use IQ Service to execute the power shell scripts. But when I execute the script I see below error . can you please help me on this
10/22/2024 10:55:40 : RpcHandler [ Thread-46 ] ERROR : “Malformed request received from client - Q01RAP004.amerus.corp.tld:55010. Received header length as - Error in parsing - Input string was not in a correct format.”
The error message you’re encountering suggests an issue with the format of the request being sent to the IQService. Please check below
Ensure that the input string being passed to the PowerShell script adheres to the expected format. Review how parameters are constructed in your RpcRequest.
You can test it independently the script in a PowerShell console.
Ensure that the IQService is properly configured to handle RPC requests. Check logs for any additional error messages that might provide more context.
Thanks. I am able to successfully run the RPC request now. I ran into a different issue now, I see that the script file is getting generated in the IQ Service folder. But the script is not actually getting executed. When i execute the script manually from powershell , it works fine and appends the file. But it is not getting executed from sailpoint.
please provide your inputs on this.
I have installed, IQService without any user and the file that needs to be appended is also in the IQService Folder.
I have validated few things such as
Checked if RSAT is installed on the windows server
Checked if there is a permission issue for the folder
Everything looks good. the powershell script is executed from SailPoint rule and there is a local copy has been created under IQService folder, but the script is not getting executed on the server. I receive the response as script has been executed but it is not.
The powershell i am trying to execute is a small code to append a file with a string to check if we can execute the scripts. The local file is created but the file is not created / appended ( it works as expected when I execute it with windows powershell).
Let me know if I have to check any thing.
FYI, the IQService which I am using is installed for Azure Active Directory .
We do have a different IQService for AD Connector, when I use AD IQ Service , the scripts executes successfully and the file is created / appended.
I observed few things. Mentioning these details so that other people can get some information.
We have two IQ Service
1st IQ Service - is used by for AD configuration, where GUI is not enabled and it is a windows core server
2nd IQ Service - Installed on a different Windows server , and used for Azure Active Directory where certificate based authentication is enabled to manage exchange online attributes 1st Scenario
As part of RPC Request if I pass “Azure Active Directory” application and use the 2nd IQService (that we installed recently to manage exchange online attributes from Azure connector) Application , the local file of script is generated in the IQ Service folder and script is not actually executed. 2nd Scenario
As part of RPC Request if I pass “AD” application and use the 2nd IQService (that we installed recently to manage exchange online attributes from Azure connector) Application , the local file of script is generated in the IQ Service folder and script is executed successfully.
I am able to complete the use case , but still trying to find out why the powershell script is not executed when we pass Azure application attributes to RPC request.
I will provide an update if I get any information on this. Conclusion : The powershell scripts are getting executed via IQService only if we pass “AD” application attributes to RPC Request.
if this attribute can be managed via connector , then we can directly add EXO_ in the schema. If not the other approach would be execute the powershell scripts