Click HERE to see how Saviynt Intelligence is transforming the industry. |
07/01/2024 09:08 AM - edited 07/01/2024 09:11 AM
Solved! Go to Solution.
07/01/2024 09:41 PM - edited 07/01/2024 09:46 PM
Hi @rushikeshvartak ,
Because the problem is associated with the process of accessing the graph API, the graph API does not support the expand operation for "customSecurityAttributes". Could you please locate the screenshot?
Try "?$select=id,userPrincipalName,customSecurityAttributes" It should work.
Thanks
Prafull,
07/01/2024 09:48 PM
What will be mapping in ACCOUNT_ATTRIBUTES?
"customproperty23": "customSecurityAttributes.ABC.AccountType~#~char",
Its not working
07/01/2024 10:34 PM
Hi @rushikeshvartak ,
Which error are you experiencing, if any? May I kindly request that you share the logs in order to validate the request, response, and error?
Thanks
Prafull,
07/02/2024 10:34 AM
Please find logs for pre-import preview ( expected value should come in cp23)
07/02/2024 09:19 PM
Hi @rushikeshvartak ,
I am unable to locate the "customSecurityAttributeValue" attribute value that has been retrieved by the "AzureAD" Connector while I am looking through the logs. Or there is a lack of data for the top two ids. Please check to see if the data is available, and if it is, then you ought to try REST and let me know the results.
Thanks
Prafull,
07/02/2024 09:44 PM
We know it will work with REST Connector but we don't want another connector for this use case.
07/02/2024 10:09 PM
You have attempted to store the whole "customSecurityAttributeValue" JSON in cp23, have you?
Thanks
Prafull,
07/02/2024 10:21 PM
I tried 3 variation
07/03/2024 03:19 AM - edited 07/03/2024 03:20 AM
Could you please share the Postman response of below request?
Thanks
Prafull,
07/04/2024 06:38 AM - edited 07/04/2024 07:09 AM
GET: https://graph.microsoft.com/v1.0/users?$count=true&$select=id,userPrincipalName,companyName,givenNam...
Below is the response line wrapped. Please review and share your response.
07/10/2024 02:18 PM
@prafullgoyal Please suggest solution
07/10/2024 07:53 PM
Simply delete "customsecurityattributes" from account import fields and account attribute mapping and see whether the import works properly; this will tell whether the problem is with this attribute or something else.
Technically, I believe this should work; I recently tried to fetch the "signinactivity" attribute and was successful, simply by adding it to the account import field and mapping it to a customer property with a comparable json structure.
format of that attribute is as below via postman call:
{
"@odata.context": "https://graph.microsoft.com/v1.0/$metadata#users(signInActivity)/$entity",
"id": "XXXXX",
"signInActivity": {
"lastSignInDateTime": "2024-03-22T12:53:34Z",
"lastSignInRequestId": "XX-5863-4a40-88d1-231cc93a5000",
"lastNonInteractiveSignInDateTime": "2024-03-22T12:53:40Z",
"lastNonInteractiveSignInRequestId": "c7782679-d6b6-XX-a241-f3d04d987600"
}
}
mapping it in account attributes as below worked for me,
"customproperty31":"signInActivity~#~char",
"LASTLOGONDATE":"signInActivity.lastSignInDateTime~#~date"
here first CP31 will have complete json, lastlogon will have just 2024-03-22T12:53:34Z, hope this helps.
If still facing issue , please follow the support process with all relevant logs.
07/10/2024 09:12 PM
I tried for signInActivity but did not worked and here ask is about customsecurityattributevalue
07/10/2024 09:19 PM - edited 07/10/2024 09:22 PM
07/10/2024 09:34 PM
It worked for me for signInActivity but my ask is different
07/10/2024 09:26 PM
I have provided an example to import; if it does not work, I suspect a configuration issue.
Please follow the support process with all relevant logs.
Thanks
Prafull,
07/10/2024 09:30 PM
Does it work for CustomSecurityAttributeValue for you ?
FD https://saviyntsupport.saviynt.com/support/tickets/2038795
07/10/2024 11:26 PM
Simply enter the URL below into Postman and check to see whether you are receiving the desired response.
https://graph.microsoft.com/v1.0/users?&$select=id,displayName,customSecurityAttributes
If the answer is yes, then you will need to follow on FD; otherwise, you will need to use REST.
Thanks
Prafull,
07/10/2024 11:27 PM - edited 07/10/2024 11:28 PM
Refer Postman screenshot
08/13/2024 10:03 AM
As confirmed by TAM , its not supported from OOTB Azure AD connector. It can be achieved using REST Connector.
Idea raised
https://ideas.saviynt.com/ideas/EIC-I-5932