Git Repository Interface manages Git credentials

Feature

The JOC Cockpit provides REST Web Services to

• manage Git credentials from a user's profile
  • Credentials include
    • Git Account
    • Git Server
    • Credentials: one of the following options can be used:
      • Git Password
      • Path to Git Private Key.
        • The path can be specified like this:
          • file name only: JOC Cockpit creates the directory JETTY_BASE/resources/joc/repositories/private to which the private key file has to be stored by the user. JOC Cockpit will use this directory to identify the private key file and to authenticate with Git.
          •  empty file name: JOC Cockpit will use the private key file ~/ssh/id_rsa from the JOC Cockpit account's home directory.
          • path to a file: JOC Cockpit makes use of the indicated path to a private key file
        • User actions:
          • For the private key file users have to specify read/write permissions for the user only (octal: 600)
          • Users are free to create a ~/ssh/config file for further specification of private key locations
      • Git Access Token
  • Specification of the Git Account is required, one or more out of Git Password, Git Private Key and Git Access Token have to be specified when using the REST Web Service.
  • Credentials are managed in line with JOC Cockpit security levels:
    • LOW: credentials are managed with the root account only.
    • MEDIUM: credentials are managed on a per user basis
    • HIGH: no credential management is available.