Custom properties and Auto-create customer #82
Replies: 5 comments
-
Hello @HappyPathAB , LicenseeServices.update() operation can be used to update |
Beta Was this translation helpful? Give feedback.
-
New Feature Request issue added to the Core backlog. |
Beta Was this translation helpful? Give feedback.
-
So this means in effect that custom properties can't be set when using auto-create customer -- because you don't want to include an Operation-level API key in code shipped to clients. Is my understanding correct that this is a limitation on the server side and not just in the C# API? Sorry if this seems dense, but there's no "Core" repository on the Labs64 GitHub page so I'm not sure what your feature request comment means. |
Beta Was this translation helpful? Give feedback.
-
Hi @HappyPathAB sorry for the confusion - I was referring to the NetLicensing Core services (serving RESTful API). Until this will be addressed, the above workaround with the LicenseeServices.update() can be used. |
Beta Was this translation helpful? Give feedback.
-
NetLicensing v2.8.16 introduced specifying of the custom properties for new customers on validate call. Example: curl -X POST --header 'Content-Type: application/x-www-form-urlencoded' \
--header 'Accept: application/xml' \
--header 'Authorization: Basic <obscured>' \
-d 'productNumber=P93DQU34K¶m1=value1¶m2=value2' 'https://go.netlicensing.io/core/v2/rest/licensee/CUST-T03/validate' ... results in the customer properties / tags set in the customer profile: |
Beta Was this translation helpful? Give feedback.
-
I am using the C# API and have a product set to auto-create customer.
If I include custom properties in the initial
validate()
call which creates the customer, they don't seem to be honored. They're not returned in the response, nor in subsequent validation responses.Is it not possible to include custom properties in this call?
Or am I doing something wrong?
Beta Was this translation helpful? Give feedback.
All reactions