|
Post by AMI_Mani on Jun 8, 2020 7:06:58 GMT
Hi,
As per AccountService.v1_6_0.json, Authentication is described as below
"Username": {
"description": "The user name for the Service.",
"longDescription": "This property shall contain the user name for this Service.",
"readonly": false,
"type": "string",
"versionAdded": "v1_3_0"
}
When the service runs for first time, Activedirectory, LDAP username will not be available and it will be null in get response of AccountService for first time, so that user can patch the property
But if we show null, it's not according to schema.
Is this mistake in schema or do we need to show "" for username, if not exists
There is no way to set Authentication also null
"Authentication": {
"$ref": "#/definitions/Authentication",
"description": "The authentication information for the external account provider.",
"longDescription": "This property shall contain the authentication information for the external account provider.",
"versionAdded": "v1_3_0"
},
Thanks,
Mani
|
|
|
Post by mraineri on Jun 8, 2020 12:44:19 GMT
This would need to be an empty string until someone configures the property. Using null would indicate some sort of error when reporting the property.
Other strings that are purely user configurable (like AssetTag) follow this methodology as well.
|
|