Dot notation support for SCIM 2.0 sub-attributes

There is a known issue with using dot notation for SCIM 2.0 operations on sub-attributes within an entry.

The PingDirectory server can’t properly interpret the dot notation that defines sub-attributes in the SCIM 2.0 standard. To perform the desired operation, modify your SCIM statements by defining any sub-attributes as child objects of the parent attribute.

For example, when updating complex or extended SCIM attributes, don’t use these formulations, which rely on dot notation to define the sub-attribute:

\\ Incorrect complex attribute example
	{
	  "schemas":[
	    "urn:ietf:params:scim:api:messages:2.0:PatchOp"
	  ],
	  "Operations":[
	    {
	      "op":"replace",
	      "value":{
	        "name.formatted":"test1 test2",
	        "name.familyName":"test1"
	      }
	    }
	  ]
	}

\\ Incorrect extended attribute example
{
  "schemas":[
	"urn:ietf:params:scim:api:messages:2.0:PatchOp"
  ],
  "Operations":[
	{
	  "op":"replace",
	  "value":{
		"urn:ietf:params:scim:schemas:extension:myown:2.0:User.lastname":"test3",
		"urn:ietf:params:scim:schemas:extension:myown:2.0:User.section":"test4"
	  }
	}
  ]
}

Use the following formulations instead:

\\ Correct complex attribute example
	{
	  "schemas":[
	    "urn:ietf:params:scim:api:messages:2.0:PatchOp"
	  ],
	  "Operations":[
	    {
	      "op":"replace",
	      "value":{
	        "name":{
	          "formatted":"test1 test2",
	          "familyName":"test1"
	        }
	      }
	    }
	  ]
	}

\\ Correct extended attribute example
	{
          "schemas":[
                "urn:ietf:params:scim:api:messages:2.0:PatchOp"
          ],
	  "Operations":[
	    {
	      "op":"replace",
	      "value":{
	        "urn:ietf:params:scim:schemas:extension:myown:2.0:User":{
	          "lastname":"test3",
	          "section":"test4"
	        }
	      }
	    }
	  ]
	}