Description of problem: There is no validation in place to block a user from adding a disabled activation key to a kickstart profile. This prevents a system from registering properly after kickstart completes: Error Message: Could not find token '3c4391141b17fb87c61aa0ec8435adfe' Error Class Code: 60 Error Class Info: Invalid system registration token Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. Create an activation key. 2. Click on the key list and uncheck the "Enabled" box next to that key to disable it. 3. Create a kickstart profile. 4. Add the key to the kickstart profile. Actual results: This is allowed. Expected results: This should be blocked. Additional info:
* Added KickstartLister.getActiveActivationKeysInOrg() which retrieves all the activation keys for a given org which are not disabled. * Changed ActivationKeysSetupAction to use this new call These two changes should prevent disabled keys from showing up in the list at all.
Testing Suggestion 1) Create an activation key 2) Click on the key list and uncheck the "Enabled" box next to that key to disable it. 3) Create a kickstart profile 4) Attempt to add the key created in step #1 to the profile Expected Result - The key should not show up in the list of keys available to be added to the profile. All disabled keys are now ommitted from the "add to profile" list.
I have attempted to add a few disabled keys to a Kickstart profile and it no longer shows up in the available list. This looks good to me, so I'm moving it to VERIFIED.
QA Contact -> ssalevan
moving to closed - currentrelease