The path with which the credential will be used. The remote hostname for a network credential. The protocol over which the credential will be used (e.g., https).
The list ofĪttributes is terminated by a blank line or end-of-file. Is no quoting, and one cannot transmit a value with newline or NUL in it). In both cases, all bytes are treated as-is (i.e., there The value may containĪny bytes except newline or NUL. The key may contain any bytes except =, newline, or NUL. EachĪttribute is specified by a key-value pair, separated by an = (equals) sign, followed by a The credential is split into a set of named attributes, with one attribute per line. The actual credential data to be obtained (login/password). This information can correspond either to keys for which git credential will obtain the login/password information (e.g. INPUT/OUTPUT FORMAT git credential reads and/or writes (depending on the action used) credential information
The credential description obtained from step (2) (which also contain the ones In either case, git credential should be fed with If the credential was rejectedĭuring the operation, use the "reject" action so that git credential will ask for a Tell git credential to reuse it in its next invocation. Operation to complete successfully, then it can be marked with an "approve" action to Report on the success or failure of the password.
GIT COMMAND LINE LOGIN PASSWORD
Use the credential (e.g., access the URL with the username and password from stepĤ. Unlocked) before it returned password=secr3t.ģ. Keychain instead, or no user interaction was done if the keychain was already User actually typing this password (the user may have typed a password to unlock the If the git credential knew about the password, this step may not have involved the The path attribute when the protocol is HTTP(s) and eHttpPath is false. Output, but Git may also modify the credential description, for example by removing In most cases, this means the attributes given in the input will be repeated in the the login and password) will be produced on standard output, like: The complete credential description (including the credential per se, This isĭone by running git credential fill, feeding the description from step (1) to its Ask git-credential to give us a username and password for this description. Git credential that the application finished feeding all the information it has):Ģ. The following credential description (don’t forget the blank line at the end it tells Generate a credential description based on the context.įor example, if we want a password for, we might generate If the action is approve or reject, no output should be emitted.Īn application using git-credential will typically use git credential following theseġ. If the action is reject, git-credential will send the description to any configuredĬredential helpers, which may erase any stored credential matching the description. If the action is approve, git-credential will send the description to any configuredĬredential helpers, which may store the credential for later use. The username and password attributes of theĬredential description are then printed to stdout together with the attributes already If the action is fill, git-credential will attempt to add "username" and "password"Īttributes to the description by reading config files, by contacting any configuredĬredential helpers, or by prompting the user. Reject) and reads a credential description on stdin (see INPUT/OUTPUT FORMAT). Git-credential takes an "action" option on the command-line (one of fill, approve, or Internal C API see the Git credential API for more background on the concepts. The design of this scriptable interface models the The git-credentialĬommand exposes this interface to scripts which may want to retrieve, store, or prompt forĬredentials in the same manner as Git. Helpers, as well as prompting the user for usernames and passwords.
Git has an internal interface for storing and retrieving credentials from system-specific Git-credential - Retrieve and store user credentials
0 kommentar(er)
