No, there's no way to examine it. Why would you want to?
Hi,
We got a ActivationRequest.xml from a client and would like to know which product key he used to product this activationrequest. The content of the "ablock" xml element in the request is somehow coded or encrypted. Is there a way to extract the product key from it?
Thank you in advance
No, there's no way to examine it. Why would you want to?
The client says the activation is not working and we think that he is using the wrong product key for a specific system (it depends as there are very specific licence features). Now we cant find out if he is just using the wrong product key for the activation or if there is another problem.
You encrypt the ActivationRequest client side with an integrated obfuscated key which you dont want to publish, is that true?
You encrypt the ActivationRequest client side with an integrated obfuscated key which you dont want to publish, is that true?
There's encryption, yes. He could tell you the key he was using. If you tell me the error he's getting we could give you some help. ("activation is not working" is not enough info).
Its just a mess. No they cant tell us which key they were using, because is seems as they dont know, thats why _we_ would like to find out which key he used... 😉
Very possibly they cant activate because their responses are mixed up --> activation reponse for "system A" on "system B" and vice versa... They have several installations running with different license features, as said before.
It would be a nice feature to be able to identify the productkey which was used to generate the request. Of course you can do it (otherwise you dont know which key to activate), you just dont want me to do it. 🙄
You can get the product key in your app using GetPKey(). You can display it to the user. Also, they can re-generate the activation request file.
Thats what we are going to ask them to do (regeneration of ActivationRequest).
Our problem is that the end user is very remote and each transport of request and response file is complicated, not for free and time consuming. So we just hoped to have the possibility to give a better feedback like "you have to use key xyz on system abc and not on system qrs".
But anyway thank you
Honestly, the easiest thing to do, if they can't handle the activation request files (which aren't terribly complicated), is to just use online activation. With online activation everything is magically handled. Of course they need to allow outgoing connections to wyday.com.