Cleanup Essex_Hog, update authentication docs #50
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To authenticate to Confluence Server or Datacenter using a PAT (Personal Access Token) (Bearer token), it should NOT be base64 encoded.See https://confluence.atlassian.com/enterprise/using-personal-access-tokens-1026032365.htmlThis was already working for JIRA/Gottingenhog, but not yet for Confluence/Essexhog.I also made sure all variables in EssexHog are named
confluencexxxx
to avoid any confusion with GottingenHog.Ideally the authentication is extracted into a shared piece of code ("atlassian auth"), but since this is my first Rust code change ever, I didn't dare to go that way :-)
Updated docs a little bit as well to help people deciphering the differences between Cloud and Server/Datacenter authentication which are handling the PATs differently.