Bug 496731 - Multi-org - reactivation key created through UI does not include org id
Summary: Multi-org - reactivation key created through UI does not include org id
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: WebUI
Version: 530
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Shannon Hughes
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: 462714
TreeView+ depends on / blocked
 
Reported: 2009-04-20 20:49 UTC by Brad Buckingham
Modified: 2014-05-09 10:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-09 10:37:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Brad Buckingham 2009-04-20 20:49:54 UTC
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'

Comment 1 Clifford Perry 2014-05-09 10:37:55 UTC
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


Note You need to log in before you can comment on or make changes to this bug.