Unable to use cert credentials in newer version of plugin

[shapiroj]

We are using cert credentials with version 1.10.2. We'd like to upgrade to version 1.11 for the pipeline support. However, cert credential usage was disabled with 460d423, pointing to some brokenness with a previous commit. Are there any more details on this (https://github.com/jenkinsci/stashnotifier-plugin/pull/98/files?), and is it possible to get this feature re-enabled?

[Rykus0]

For me and my team, SSH is the only authentication method available.

[scaytrase]

How certificates are related with SSH, can you explain? Maybe I just misunderstand something, but for me SSH stands with SSH keys and SSL with Certificate credential authentication via SSL

[Rykus0]

I guess I misunderstood, and maybe this is a different issue. SSH credentials are not available as choices for the plugin - only username and password. I guess I was equating an SSH key to a certificate - my apologies.

[scaytrase]

SSH keys are no way to use for HTTP API requests, unfortunately

[Rykus0]

Ok, so I guess this plugin doesn't do what I thought, because what I'm thinking (updating the build status) doesn't need any authentication. I'll just create a shell script or something to run post-build and do it with curl. Sorry for muddying up this thread.

[scaytrase]

Generally this plugin does the same - it just performs http api call with json payload, but I really doubt that you can modify Bitbucket data (mark builds) without access to certain repository.

Documentation says the following:

The authenticated user must have LICENSED permission or higher to call this resource.

https://developer.atlassian.com/static/rest/stash/latest/stash-build-integration-rest.html#resources

[Rykus0]

Ok, maybe I was logged in when I did it before. I guess I need to burn a license just so Jenkins can report build status back... I'll figure it out. Again, sorry for putting all this here.

[shapiroj]

Any ideas on the original problem? Cert credentials are no longer usable for the notifier plugin.

[scaytrase]

@shapiroj I've no idea how to reproduce or test this, since the setup is very uncommon, so if you'll provide a PR with some kind of fixes we can make things faster