You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I made changes to dependabot-core to support the bitbucket server source.
Everything is working fine. I started using cli verify certain things a few days back and everything was working fine even without specifying the credentials, for example input
I think the proxy is not passing credentials as bearer tokens.
Is the code available in public for ghcr.io/github/dependabot-update-job-proxy/dependabot-update-job-proxy:latest ?
The text was updated successfully, but these errors were encountered:
noorul
changed the title
Credentials issues when using custom source provider for bitbucket server
Credential issues when using custom source provider for bitbucket server
Aug 3, 2023
The proxy isn't currently open source. I'm personally interested in changing that, but I can't speak for the company and that's a much bigger discussion for us internally, so don't hold your breath anytime soon.
As far as the token settings though, can you document here what you're seeing from the proxy vs what you'd like to see sent? I think I know what you're asking for, but it'd be helpful if it was super clearly stated what you're looking for.
I made changes to dependabot-core to support the bitbucket server source.
Everything is working fine. I started using cli verify certain things a few days back and everything was working fine even without specifying the credentials, for example input
But all of a sudden it stopped working. Now I get the following error:
I tried several combination of setting credentials for the type git_source but not helping, for example
I think the proxy is not passing credentials as bearer tokens.
Is the code available in public for ghcr.io/github/dependabot-update-job-proxy/dependabot-update-job-proxy:latest ?
The text was updated successfully, but these errors were encountered: