Jersey JIPP - job with API access instead of central-publishing-maven-plugin access

Summary

I'd like to implement a job, which uses the Portal Publisher API instead of central-publishing-maven-plugin to check status and publish/delete deployments using the Jersey bot.

Steps to reproduce

using curl with --basic -u 'name:password or --header "Authorization: Bearer ${BEARER}" where $BEARER is base64 of username:password

What is the current bug behavior?

However, now this seems not possible because password in the settings.xml is already encoded via base64.

What is the expected correct behavior?

Do you have any relevant documentation or advice on how to do this?

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

would help automate releases and artifact management.