Merge pull request #2901 from RestComm/github2900

allow undefined properties at profile doc level

Author: maria-farooq

restcomm/restcomm.docs/sources-asciidoc/src/main/asciidoc/api/profile-api.adoc

@@ -20,7 +20,14 @@ REST API. The Default Profile Sid is "PRae6e420f425248d6a26948c17a9e2acf"
 
 Since the Profile configuration is expected to grow as required, the Profile entity
 is defined by a JSON schema, rather than regular properties, representing a 
-document used as generic container.
+document used as generic container. 
+
+The REST API will validate well-known contains
+of the document that are used by RestcommConnect during session handling logic. The
+rest of the document will not be validated, with the only constraint of a 
+maximum size limitation of 10MB. This means the REST API consumer may use the Profile
+document to store/retrieve any kind of arbitrary information as long as the document is 
+a valid JSON document.
 
 All Profiles REST API is only accesible by SuperAdmin credentials. With the exception
 of reading the associated Profile, where all Roles are allowed if the queried profile

restcomm/restcomm.http/src/main/resources/org/restcomm/connect/http/schemas/rc-profile-schema.json

@@ -1,7 +1,7 @@
 {
     "$schema": "http://json-schema.org/draft-04/schema#",
     "id": "resource:/org/restcomm/connect/http/schemas/rc-profile-schema.json#",
-    "additionalProperties": false,
+    "additionalProperties": true,
     "type": "object",
     "properties": {
         "featureEnablement": {

restcomm/restcomm.http/src/test/resources/org/restcomm/connect/http/schemas/freePlan.json

@@ -22,5 +22,6 @@
             "time" : 30,
             "timeUnit" : "days"
         }
-    }    
+    }   
+    ,"planSubscriptionDisplay" : true
 }