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 have a generic (Apache with mod_auth2, and Keycloak) remote repo, and I'm trying to set up a Windows client to access this repo. This basically works, but there's a problem. The client info is:
Windows 10 (22H2) Git for Windows, 2.47.1.windows.2 GCM, 2.6.1
This works for both fetch and push, but it contains the client secret in plaintext, which is obviously an issue. My procedure is:
Clone a repo; this pops up a browser window
Enter a username and password; a new window pops up for the TOTP
Enter the TOTP
The repo clones correctly
Comment out or delete the oauthClientSecret line
GCM creates ~/.gcm with the dpapi information, which appears to be valid. I can then fetch/push/etc for about 10 minutes without entering any credentials. However, after 10 minutes, the client secret is forgotten, and I need to log in again. Why?
GCM does pop up another window asking for a username and password, but I can't find a combination of username and password which works. The only solution appears to be to leave oauthClientSecret in the config file, so dpapi appears to be useless after 10 minutes. Apache does appear to be correctly set up for refreshing tokens.
Can anyone suggest a fix for this? Log attached, if it helps. logs.txt
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I have a generic (Apache with mod_auth2, and Keycloak) remote repo, and I'm trying to set up a Windows client to access this repo. This basically works, but there's a problem. The client info is:
Windows 10 (22H2)
Git for Windows, 2.47.1.windows.2
GCM, 2.6.1
.gitconfig:
This works for both fetch and push, but it contains the client secret in plaintext, which is obviously an issue. My procedure is:
oauthClientSecret
lineGCM creates ~/.gcm with the dpapi information, which appears to be valid. I can then fetch/push/etc for about 10 minutes without entering any credentials. However, after 10 minutes, the client secret is forgotten, and I need to log in again. Why?
GCM does pop up another window asking for a username and password, but I can't find a combination of username and password which works. The only solution appears to be to leave
oauthClientSecret
in the config file, so dpapi appears to be useless after 10 minutes. Apache does appear to be correctly set up for refreshing tokens.Can anyone suggest a fix for this? Log attached, if it helps.
logs.txt
Beta Was this translation helpful? Give feedback.
All reactions