Page 1 of 1

Token for end customers

Posted: Thu Jul 26, 2018 8:25 am
by weickert_emc
As a software manufacturer for our end customers, we supply the necessary components,
so that our customers can use the components provided by PTV.
In order to do this, we would like to provide each customer with their own token,
that is then used by the end user to use the components.

Question: Is that possible? How and where exactly is such a token created.

Re: Token

Posted: Thu Jul 26, 2018 8:46 am
by Bernd Welter
Hello Andre,

that is a good question and our answer is this:

Access to our PTV xServer Internet environments always requires credentials (username="xtok", password is the TOKEN) whether it is the TEST, INTEGRATION or PRODUCTION system. The token for TEST and INTEGRATION differs from the PRODUCTION token. No matter whether you are partner or end customer: for PRODUCTION we have to create a new, usecase specific TOKEN. From a technical perspective I recommend that you prepare an application for initial customization through config settings such as "endpoint" and "token" which will then simply have to be configured with the values you get after licensing for production purpose.
  • As a value added reseller (=VAR = partner who created an own application that is sold to third parties) you can create your own regular account on xServer INTERNET. Please be aware to get a standard VAR contract via your partner manager.
  • You get access to TEST and INTEGRATION so you can develop your application.
  • As a VAR you can order further licenses for your end customers. These additional licenses get access to PRODUCTION of the corresponding maps.
  • You can also order "a stock" of standard licenses in advance. This will help you to avoid waiting times. Of course each additional license has to be restricted to the future use.
  • As soon as your first additional end customer productive license is use we start the billing process. The bills will be sent to the VAR including the the additionallicense contract numbers. The VAR is responsible for forwarding the specific sub-bill to his end customer.
Does this answer the question?

Best regards,
Bernd

PS: is there a difference compared to OnPremise? Yes it is: by default the OnPremise server is configured to work with HTTP instead of HTTPS and it does not require authentication. But you can refit both HTTPS and enforced authentication and further mechanisms if you want. But what is different: to start an OnPremise server you need a so-called license file which will be designed as follows:
  • termination date : test = about 6 months from when you request it / production = annual base (1.1.20xx)
  • Ienvironmental settings : test = not applied / production = restricted to IP range
  • feature wise : test = not applied / production = restricted to what you licensed

Re: Token for end customers

Posted: Thu Jul 26, 2018 8:58 am
by weickert_emc
QUestion :
So I'm mentally on the page "https://ae.mapandguide.de/xservershop/" and order there for each of our customers a new license?

Is this correct?

Re: Token for end customers

Posted: Thu Jul 26, 2018 9:17 am
by Joost
No, that is our older deprecated licensing system. For obtaining tokens for your end customer you need to contact your sales representative.

Re: Token for end customers

Posted: Thu Jul 26, 2018 11:24 am
by Bernd Welter
Hi there,

I'd say the answer depends on when you joined. Those partners who are using the legacy shop can buy their additional licenses as descibed above. New partners have to negotiate each new end customers with their partner managers.

Here are some screenshots for the legacy users:
Log in into the admin engine
Log in into the admin engine
Select the kind of license you want to buy
Select the kind of license you want to buy
Provide the end customers sub-account  data
Provide the end customers sub-account data
Validate it
Validate it
Check the overall list of your licenses
Check the overall list of your licenses
Gather the token of the new account
Gather the token of the new account
Maybe this helps.

Best regards,
Bernd