Git material are caching username or password

[Kleber Rocha]

I have a problem with material, when I configure a material using Git, everything is fine, but if I need change the user, the material doesn't work, only I revert to old user the material can clone.

Someone has faced this issue?

Thank you

[Kleber Rocha]

I forgot about the infos:

Gocd 19.9.0

Here is the output from agent

[go] Start updating files at revision e63218abcc36671bcb1a0af3467bae12ec10b0f9 from https://bitbucket.org/XXXXXXX.git
STDERR: Cloning into '/go/pipelines/XXXXX'...
STDERR: remote: Invalid username or password
STDERR: fatal: Authentication failed for 'https://bitbucket.org/XXXXXX/'
Failed to run git clone command

[Aravind SV]

Hello!

GoCD doesn't cache any credentials for git materials. What usually caches credentials is git's credential helper. More documentation is available here:
https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage

This depends on the operating system and the configured helper. I'd start looking there.

Cheers,
Aravind

[Kleber Rocha]

Hello Aravind,

I forgot to inform that I'm only using elastic agent on kubernetes, in this way, I think that credential cannot store in the images.

Cheers,

Kleber

[Aravind SV]

Hello Kleber,

On Mon, Oct 28, 2019 at 14:59:43 -0700, Kleber Rocha wrote:
> I forgot to inform that I'm only using elastic agent on kubernetes, in this
> way, I think that credential cannot store in the images.

If that's the case, where are you changing the user? You mentioned you need to change it, but the URL seems to be: https://bitbucket.org/XXXXXXX.git and not https://us...@bitbucket.org/XXXXXXX.git or something of that sort.

Cheers,
Aravind