I replaced my expired API key in the forge but my ...
# puppet
y
I replaced my expired API key in the forge but my Puppet core test nodes are still getting HTTP 401 responses when trying to
dnf update
. Yes, I updated the 'password' value with the new API key. Yes, the user name is 'forge-key'.
j
Hey Colby, is this issue still happening for you today? I had some tests that ran last night and successfully downloaded Puppet Core using Forge API key auth, so the system was responding last night, but I also didn't see failures on Saturday or Friday night related to that. I'm assuming it was working previously? Have you tried manually going to the endpoint in a browser and entering the forge-key and API key values to see if it works that way?
y
Still failing. I tried it in the browser with
forge-key
as the user name and the token as well. I see the token information updated in forge.puppet.com (Last used shows my latest attempts).
I created a 2nd token and it fails as well.
j
Okay, thanks for checking through the browser. Has this ever worked with the specific account or organization you are using? Sometimes it's not the key being invalid, but rather the account is in a state that means it doesn't have permission to download. For example, if the EULA isn't signed or there isn't a customer license tied to the organization.
y
I checked my profile and it shows I signed the EULA
image.png
Okay ... weird. I used an API key that does not appear to be associated with my account (one I had laying around in a different .repo file on my computer) and it works fine.
Ah, okay. It looks like I tried using an org-specific API key, not my user one.
j
Aha! Good detective work. Yup, if the organization you have the API key associated to doesn't have some sort of license or association to having purchased, then its API keys won't be able to be approved as being authorized to get the software, even if they are valid otherwise. Should your organization have access? If so, we should get you in with support so they can start digging in and fixing up the customer organization so it is tied correctly to the company licensing. If you're acting as a dev, using the free developer tier, then API keys on your personal account should do the trick to let you download (since you signed the EULA).
y
Yeah, this is for my personal playground/dev access. No org of mine should have an authorized API key.
j
Perfect, good luck with getting the playground set up!