-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
None
Per STSP-5244:
"For cloning and pushing Repositories with Bitbucket Server (as well as LFS), User-Session will be verified with existing Cookies.
How can we configure SourceTree with embedded git, to set/get Cookies?"
We currently do not have this ability, so this ticket is for research.
Follow-up:
"we use Bitbucket and also Sourcetree behind a appliance for authentification and ssl offloading.
The company policy is that this appliance must validate every http user (also souretree/git client) e.g. we must accept access (for selected customer) via internet.
A none lfs push needs here 3 separate requests and so 3 times a validation because the only way to prevent revalidation is a cookie to remember the client. On a lfs push we fail because the lfs client will not send username/password on a PUT.
The second possible way to do persistence via source address is not possible because we must support proxy access where many users sharing one ip
So at this time we have a lot of overhead with none lfs and we are unable to use the lfs client."
Enable using Cookies in SourceTree with embedded git
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
None
Per STSP-5244:
"For cloning and pushing Repositories with Bitbucket Server (as well as LFS), User-Session will be verified with existing Cookies.
How can we configure SourceTree with embedded git, to set/get Cookies?"
We currently do not have this ability, so this ticket is for research.
Follow-up:
"we use Bitbucket and also Sourcetree behind a appliance for authentification and ssl offloading.
The company policy is that this appliance must validate every http user (also souretree/git client) e.g. we must accept access (for selected customer) via internet.
A none lfs push needs here 3 separate requests and so 3 times a validation because the only way to prevent revalidation is a cookie to remember the client. On a lfs push we fail because the lfs client will not send username/password on a PUT.
The second possible way to do persistence via source address is not possible because we must support proxy access where many users sharing one ip
So at this time we have a lot of overhead with none lfs and we are unable to use the lfs client."