### Bug description

It is really exciting to see `quarto` addressing the challenge of publishing content to Confluence!

I gave it a try but unfortunately I have not been able to connect to my on-prem Confluence.
This seems to be because on-prem versions of confluence do not have API tokens.

Instead they have personal access tokens ([PAT](https://confluence.atlassian.com/enterprise/using-personal-access-tokens-1026032365.html)).

Do you think you could support PAT, in addition to API tokens?

Note that I have tried passing a PAT instead of the expected API token but that did not work (the error was `"x-seraph-loginreason": "AUTHENTICATED_FAILED"`, and I was using `quarto-1.3.290`)

### Checklist

- [ ] Please include a minimal, fully reproducible example in a single .qmd file? Please provide the whole file rather than the snippet you believe is causing the issue.
- [ ] Please [format your issue](https://quarto.org/bug-reports.html#formatting-make-githubs-markdown-work-for-us) so it is easier for us to read the bug report.
- [ ] Please document the RStudio IDE version you're running (if applicable), by providing the value displayed in the "About RStudio" main menu dialog?
- [ ] Please document the operating system you're running. If on Linux, please provide the specific distribution.
- [ ] Please provide the output of `quarto check` so we know which version of quarto and its dependencies you're running.
allenmanning
2023-03-29T10:22:11Z
mwouts
bug enhancement publishing-confluence epic
Future
closed
Could you support PAT for authentication on on-prem Confluence?
https://github.com/quarto-dev/quarto-cli/issues/5017