Right now the GUID is not sent to Unraid to validate. I’d like to begin sending the GUID as part of the initial buildout, to facilitate users having valid Unraid licenses when they boot the OS.
This then responds with JSON containing a bunch of fields. The response is not needed, however, as if the endpoint “403” errors, it means the GUID is invalid.The drive should only be allowed to be used if it does not get a 403 when plugged into the USB creator and the GUID is sent to this endpoint.
Right now the GUID is not sent to Unraid to validate. I’d like to begin sending the GUID as part of the initial buildout, to facilitate users having valid Unraid licenses when they boot the OS.
We have an endpoint : POST https://keys.lime-technology.com/validate/guid that can be passed the guid in the body (URLEncoded).
This then responds with JSON containing a bunch of fields. The response is not needed, however, as if the endpoint “403” errors, it means the GUID is invalid.The drive should only be allowed to be used if it does not get a 403 when plugged into the USB creator and the GUID is sent to this endpoint.