ctrlX OS - Licensing API - device key not found

[WolfgangDannert]

Hello,

I would like to test the new feature as described in this guide:
https://github.com/boschrexroth/ctrlx-automation-sdk/blob/main/doc/licensing.md#spoofing

When I send a license request with the corresponding query parameter set to the 'license-manager/api/v1/license?signResponse=true' url the server response is "device key not found":

I use ctrlX OS V2.6.1.

What do I have to do to make the REST call work?
Thank you in advance

[WolfgangDannert]

Is there anyone here who can help?

[mlaml]

Hi,

this functionality requires a device key & certificate. Could you please check whether such a key / certificate is (already) present on your device? You can check in "Settings -> Certificates & Keys -> Permanent storage -> Certificates": A file named device.crt must be presented.

Some (technical) background: The device certificate is the default trust anchor on the device used for licensing (and potential other scenarios). It was introduced not too long ago and is being shipped with devices that have ctrlX OS version 0120.7 or newer pre-installed. In case no device certificate is present, on Rexroth devices the serial number is accepted for licensing. This allows us to remain backwards compatible to devices which have not been shipped with a device certificate. Unfortunately, such devices do not support signed responses due to the missing key / certificate. We will soon offer a solution which allows to register such devices and to retrieve a device certificate.

[WolfgangDannert]

Hi,

thanks for the answer and the background information.

Only the certificate "devicePortalDeviceCert_undeletable.pem" is available.
That explains the behavior.

I have some questions about the device certificate.
Will there always be a serial number in the future or is it planned to replace it completely with the device certificate?

Will it be possible to activate software licenses on the serial number and the device certificate in the Rexroth License Portal?

When is the new "Register" feature scheduled?