Description of problem: if the AK is already created and a malicious user gets it somehow then it can be used to register hosts without any other information which will be missuse of subscription counts. 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. Version-Release number of selected component (if applicable): satellite 6 Additional info: https://bugzilla.redhat.com/show_bug.cgi?id=1095435
The user can already create keys that are e.g. 32 characters long. And it's definitely a good practice if the AK is not something that people could guess or easily read over shoulder. Each key can have a description which users can search by. We should perhaps display it also in the table where we list activation keys. Would that work?
+1 to the feature, setting team_triaged flag