Hi There,
Just along this lines,am stuck at place the CA IDM never trigger the patch operation to GW policy.It complains with the following error in the CA IDM scim log,
MODIFY operation was skipped as a result the call didn't reach to gateway. See below log extracted for your reference,i couldn't find any thing beyond this in the log.
2019-08-26 14:34:12,997 82920686 [ApacheDS Worker-thread-69] Spirng_endPointType_scim_custom_spring_endPoint_sharath (AssocAttributeOpProcessorProxy.java:192) DEBUG - MODIFY:Find assoc related modification items in: [email]
2019-08-26 14:34:12,997 82920686 [ApacheDS Worker-thread-69] Spirng_endPointType_scim_custom_spring_endPoint_sharath (AssocAttributeOpProcessorProxy.java:297) DEBUG - MODIFY:No attributes suitable for associative processor(s) found
2019-08-26 14:34:12,997 82920686 [ApacheDS Worker-thread-69] Spirng_endPointType_scim_custom_spring_endPoint_sharath (SCIMAttributeStyleOpProcessor.java:480) DEBUG - Modifying 786987 of objectClass User
2019-08-26 14:34:12,997 82920686 [ApacheDS Worker-thread-69] Spirng_endPointType_scim_custom_spring_endPoint_sharath (SCIMAttributeStyleOpProcessor.java:489) DEBUG - Using HTTP PATCH method for object modification
2019-08-26 14:34:12,997 82920686 [ApacheDS Worker-thread-69] Spirng_endPointType_scim_custom_spring_endPoint_sharath (SCIMAttributeStyleOpProcessor.java:887) DEBUG - Lookup 786987 of objectClass User
2019-08-26 14:34:13,013 82920702 [ApacheDS Worker-thread-69] Spirng_endPointType_scim_custom_spring_endPoint_sharath (AssocAttributeOpProcessorProxy.java:392) ERROR - class com.ca.jcs.scim.SCIMMetaConnector: scim_custom_spring_endPoint_sharath [eTDYNDirectoryName=scim_custom_spring_endPoint_sharath,eTNamespaceName=Spirng_endPointType,dc=im,dc=etasa]: class com.ca.jcs.assoc.AssocAttributeOpProcessorProxy: failed call on public abstract void
com.ca.jcs.processor.OpProcessor.doModify(com.ca.jcs.ObjectInfo,javax.naming.directory.ModificationItem[]) throws javax.naming.NamingException MODIFY operation was skipped
Original Message:
Sent: 05-10-2016 05:43 AM
From: Ronald DSouza
Subject: Re: IDM Operation (Replace HTTP method Patch with Post)
Hi Zhijun, thank you for the reply, i manage to get this resolved. It was the SCIM ServiceProviderConfigs file that is required by the application
Sample URL : https://<domainname>/path/ServiceProviderConfig
{
"schemas": ["urn:scim:schemas:core:1.0"],
"documentationUrl":"http://example.com/help/scim.html",
"patch": {
"supported":false
},
"bulk": {
"supported":false,
"maxOperations":1000,
"maxPayloadSize":1048576
},
"filter": {
"supported":true,
"maxResults": 200
},
"changePassword" : {
"supported":false
},
"sort": {
"supported":false
},
"etag": {
"supported":false
},
"xmlDataFormat": {
"supported":false
},
"authenticationSchemes": [
{
"name": "HTTP Basic",
"description": "Authentication Scheme using the Http Basic Standard",
"specUrl":"http://www.ietf.org/rfc/rfc2617.txt",
"documentationUrl":"http://example.com/help/httpBasic.html",
"type":"httpbasic"
}
]
}
I just had to set the patch option to false and everything work as either POST(for new records) or PUT(for modify records)