Project

General

Profile

Actions

Feature #5615

closed

[RFE] activation key - add a secure "key" field to be used instead of name when registering

Added by Thomas McKay almost 10 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Activation Key
Target version:
-
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Instead of having users register by activation key name, a more secure "key" should be available (eg. 32 character hash or similar). In this manner they could still name activation keys with readable/referencable names but would use the cryptic key with subscription-manager.

Actions #1

Updated by Thomas McKay almost 10 years ago

  • Bugzilla link set to https://bugzilla.redhat.com/show_bug.cgi?id=1095435
Actions #2

Updated by Eric Helms over 9 years ago

  • Triaged changed from No to Yes
Actions #3

Updated by Eric Helms over 8 years ago

  • translation missing: en.field_release set to 70
Actions #4

Updated by Bryan Kearney over 8 years ago

  • Category changed from 81 to Activation Key
Actions #5

Updated by Eric Helms over 8 years ago

  • translation missing: en.field_release changed from 70 to 86
Actions #6

Updated by Eric Helms about 8 years ago

  • translation missing: en.field_release changed from 86 to 114
Actions #7

Updated by John Mitsch over 4 years ago

  • Status changed from New to Rejected
  • Target version deleted (Katello Backlog)

Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.

Actions

Also available in: Atom PDF