Versions Compared

Old Version 2

changes.mady.by.user Jon Espen Ingvaldsen

Saved on

compared with

New Version 3

changes.mady.by.user Steinar Line

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

Not all Git clients support Kerberos. Git client which do not support clients will often not be able to understand the Kerberos-related HTTP headers, and will simply fail to communicate with a Kerberos-enabled Git HTTP server. We do support only Kerberos over the HTTP/HTTPS protocol, not over SSH. Also the GIT LFS protocol does not support Kerberos at all.

Info

If you are setting up Kerberos for Git and want to use a CNAME as your host name of Bitbucket, please note the following:
While browsers are using the CNAME for looking up the A record and uses this when requesting a Kerberos ticket, your Git client will not. The Git client will request for a Kerberos ticket using the CNAME. Therefore, when using Kerberos for Git in combination with using a CNAME, you will have to create a merged keytab in K-SSO consisting of one keytab for the A record and one for the CNAME. Please contact us if you have questions to this setup.