Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom properties and Auto-create customer #5

Closed
HappyPathAB opened this issue Oct 20, 2020 · 5 comments
Closed

Custom properties and Auto-create customer #5

HappyPathAB opened this issue Oct 20, 2020 · 5 comments
Assignees
Labels
enhancement New feature or request planned Good for newcomers question Further information is requested

Comments

@HappyPathAB
Copy link

HappyPathAB commented Oct 20, 2020

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?

@r-brown r-brown added enhancement New feature or request question Further information is requested labels Oct 20, 2020
@r-brown
Copy link
Member

r-brown commented Oct 20, 2020

Hello @HappyPathAB ,
As of now LicenseeServices.validate() doesn't set custom properties upon validation.

LicenseeServices.update() operation can be used to update Liecnsee entity and set additional custom properties.
Required API Key role for this operation: ROLE_APIKEY_OPERATION

@r-brown
Copy link
Member

r-brown commented Oct 20, 2020

New Feature Request issue added to the Core backlog.

@r-brown r-brown added the planned Good for newcomers label Oct 20, 2020
@HappyPathAB
Copy link
Author

HappyPathAB commented Oct 20, 2020

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?
And one that you plan to address?

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.

@r-brown
Copy link
Member

r-brown commented Oct 20, 2020

Hi @HappyPathAB sorry for the confusion - I was referring to the NetLicensing Core services (serving RESTful API).
And you are totally right - this is not necessarly related to one of the NetLicensing client libraries, rather the change need to be implemented in API ( Core :) ).

Until this will be addressed, the above workaround with the LicenseeServices.update() can be used.

@r-brown
Copy link
Member

r-brown commented Nov 27, 2022

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&param1=value1&param2=value2' 'https://go.netlicensing.io/core/v2/rest/licensee/CUST-T03/validate'

... results in the customer properties / tags set in the customer profile:
netlicensing-validate-tags

@r-brown r-brown closed this as completed Nov 27, 2022
@r-brown r-brown self-assigned this Nov 27, 2022
@Labs64 Labs64 locked and limited conversation to collaborators Oct 29, 2023
@r-brown r-brown converted this issue into discussion #82 Oct 29, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
enhancement New feature or request planned Good for newcomers question Further information is requested
Development

No branches or pull requests

2 participants