Font-awesome: Can't authenticate to npm.fontawesome.com

[kopax]

Describe the bug

I have the following error that happened in my CI when I try to authenticate with the fontawesome registry:

npm ERR! Unable to authenticate, need: Basic realm="https://npm.fontawesome.com/"

Expected behavior

I expect to login correctly using my token

What have changed recently?

[tagliala]

Hi,

just to be sure, we are referring to Font Awesome Pro, right?

We have recently changed the .npmrc required format, please check yours

Docs: https://fontawesome.com/how-to-use/on-the-web/setup/using-package-managers#installing-pro

[kopax]

Hi @tagliala and thanks for the quick reply. Yes we are referring the Font Awesome Pro.

I have checked that page and I have configured my host globally as described in font awesome documentation

I don't see any change from the format I am using for the past years, what are they?

I am running the following:

npm config set "@fortawesome:registry" https://npm.fontawesome.com/
npm config set "//npm.fontawesome.com/:_authToken" "${NPM_FONT_AWESOME_AUTH_TOKEN}"

I have the following error:

npm ERR! code E401
npm ERR! Unable to authenticate, need: Basic realm="https://npm.fontawesome.com/"

I expect to authenticate.

If you access from a browser https://npm.fontawesome.com/ , you have a Basic auth, I am not sure what I should expect here as I have never tried before.

This happened recently, the configuration was working for year. Is it me or fontawesome server?

How to fix fontawesome npm authentication?

[kopax]

IT seems that my subscription ended on Jan 16, 2020, but I should be able to access Version 5.12.0, I have the perpetual license on it.

Edit, apparently the access to the npm registry depend on the active status of my subscription.

That's a bit a shame that we can't install the version we have actually license for using the npm registry.

I didn't know and I'd like to have a small subscription extension in order to download a copy of all pro packages of my fontawesome version that are now required by my lock files.

I also think you should send an automatic email to your customers regarding that mater because we never prepared our self for this.

[tagliala]

@kopax please send an email to [email protected], you can add a link to https://github.com/FortAwesome/Font-Awesome/issues/16094 so you don't need to explain again the issue

[kopax]

Thanks, I have just forwarded the request to [email protected], in the meantime, could you please share with me by email the archives 5.12.0 that fulfill our checksum lock file requirement (the one distributed by the npm proxy we were relying on in the past, and not the direct download available one on your website)

[supercodepoet]

@kopax I sent a response email to your request 2 days ago. Did you not receive it?

[kopax]

Unless that was the one telling me to subscribe order to get support. No, I have not received it.

[supercodepoet]

@kopax It was an email explaining that we charge for services we pay for. Some services are given us for free so we pass that along. I also stated for your case I am willing to grab what you need if you provide me the packages, version numbers, and hashes.

[kopax]

@supercodepoet I have not received it. Can you please reforward it. I am willing to get all the private and paid packages for version:

"@fortawesome/fontawesome-pro": "^5.12.0",
"@fortawesome/pro-light-svg-icons": "^5.12.0",
"@fortawesome/pro-regular-svg-icons": "^5.12.0",
"@fortawesome/pro-solid-svg-icons": "^5.12.0",

I have not received anything yet. Can you please reopen and forward those archives as you apparently offered ?

[supercodepoet]

@kopax an email was sent with a .zip attachment of the requested packages. Let me know if you don't get it.

[kopax]

@kopax an email was sent with a .zip attachment of the requested packages. Let me know if you don't get it.

Thanks @supercodepoet but I can't find your email. Could you please hint me on the timestamp and address you have emailed to?

[tagliala]

@kopax I've just sent a reminder to [email protected] with a link to this discussion.

Since this is a support ticket about FA Pro, please keep using the email.

Feel free to ping me here if you don't manage to get your files

[kopax]

Thank you, I'll watch out for their email.

[supercodepoet]

The email has been sent again. Let me know if you get it.

[kopax]

I have received the email, thank you.

[jr-k]

@supercodepoet Same problem here, I have license for 5.12.1, but I can't get dependencies from "pro" repository, can I have access to these repositories ? Thanks.

[mOewa]

Hello, same behavior here, I followed the methods with npm config and npmrc and this ended with the same error.

[tagliala]

Hi guys,

I'm going to lock here because @kopax issue is related to expired license and that needs to be solved through email support

@jr-k if you have an expired license and you want a copy of the latest packages your license can download, please send an email to [email protected]

@mOewa please send an email to [email protected]