mbegerau commented on PR #9547: URL: https://github.com/apache/nifi/pull/9547#issuecomment-2718542033
I have tested with the latest commit and I can confirm that **creating flows**, **commiting changes** and **changing versions** works with all three authentication methods. As far as I know there is no way yet to delete commits or entire flows with a git registry client. Maybe you should consider applying the access token logic (if read, then assume read+write) also to the username/appPassword flow because with the current setup you need to give the app password "account:read" permission (same reason as for access token), otherwise "repository" and "repository:write" would be enough. Since there is no "View Documentation" option for registry clients, maybe it could be helpful for the user to extend the "Authentication Type" descriptions. Here some bullet point ideas: - Basic Auth: Username (not email) and App Password (link to [documentation](https://support.atlassian.com/bitbucket-cloud/docs/app-passwords/)). List required permissions: repository, repository:read, (possibly account:read) - Access Token: (link to [documentation](https://support.atlassian.com/bitbucket-cloud/docs/access-tokens/)). List required permissions: repository, repository:read - OAuth: Only works with client credentials flow which requires OAuth consumers (link to [documentation](https://support.atlassian.com/bitbucket-cloud/docs/use-oauth-on-bitbucket-cloud/)). OAuth consumer needs to be private, and callback url needs to be set, but can have any value. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
