Can't publish on quarto-pub

[pnavaro]

I am trying to publish on quarto-pub and I am stuck in a loop hole. I always get this message

The authorization saved for Quarto Pub is no longer valid.
  Please be sure you are logged into the correct Quarto Pub account in your
  default web browser, then press Enter to re-authorize.
[✓] Creating quarto-pub site
? Re-authorize account (Y/n) › Yes
? Authorize (Y/n) › Yes

I try a lot of things:

• Delete my account on quarto-pub and recreate (I used github and I change to email+passwd)
• Remove my account with quarto publish accounts
• Remove the directory .quarto
• Change my default browser (Safari, Firefox, Chrome)
• create a token and set the env variable QUARTO_PUB_AUTH_TOKEN

Thanks for your help

Pierre

[stevecrawshaw]

yes, me too..

[salimkaplan]

I have the same. It keeps asking for authorization

[cderv]

Thanks for the report. I have open an issue to track resolution: #3941

No need to everyone comment. You can add 👍 to confirm but we are aware of the issue. Thanks

[softwarenerd]

Hi All,

We identified a configuration issue that was causing publishing to fail with an authorization error. The configuration is now fixed, and publishing is back online. We understand the root cause of the issue, so this won't happen again.

Apologies for the inconvenience!

Best,

Brian

[higgi13425]

Looks like a version of this is happening again in February 2024. I have a daily cron job which I set up after an initial manual authorization. After an unclear period, it "loses" this authentication and the cron job stops running (recently on Jan 29, 2024, again on Feb 14, 2024). Is there a way to make this authentication more durable? 2 weeks seems a bit short for an automated process. Couldn't this be set up for annual, or q6 months? Kind of defeating the point of automation with a 2 week re-auth.

[cderv]

Just to be sure and cover everything before re-opening a configuration problem

Did you set up Publishing credential in your cron-job using QUARTO_PUB_AUTH_TOKEN ?
See our doc:

• https://quarto.org/docs/publishing/quarto-pub.html#access-tokens
• https://quarto.org/docs/publishing/ci.html#publishing-credentials

If you are using the interactive way without setting up the auth token, then there is a re-auth delay by security. This is usual practice AFAIK. When doing automation using API TOKEN is recommended.

or does it happen also with QUARTO_PUB_AUTH_TOKEN set ? In that case, this is definitely something we'll have a look in quarto pub configurations.