Description of problem: When a reactivation key is created through the web-UI, the key does not include the org id; however, if it is created using the API, it does. For example, key created using web-ui might look like : 'asdfjkl' key created using api might look like : '1-asdfjkl' The intent of this BZ is to make the behavior consistent. Version-Release number of selected component (if applicable): 5.3.0 How reproducible: always Steps to Reproduce: 1. select System->System->Details->Reactivation -> Generate New Key 2. 3. Actual results: observe key as something like 'c40dff6a0a87fee1a8cea13fbefdfb1a' Expected results: if created in org 1, the expected result would be something like '1-c40dff6a0a87fee1a8cea13fbefdfb1a' Additional info: e.g. of key generation using api: >>> client.system.obtainReactivationKey(key, 1000013430) '1-5fd6d12845f99d49770eb3224bfef8f8'
We have not addressed this specific bug in over 5 years years. This does not seem to have an active customer case with the bug report either. Closing out as wontfix to clear from backlog. Please re-open if you disagree and wish further review. Cliff