Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion content/en/docs/refguide/version-control/on-premises-git.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,11 @@ Make sure you have completed the following prerequisites:

## Supported Authentication Mechanisms

Currently, Mendix only supports HTTP Basic authentication for Git service providers. With most providers, this takes the form of using of personal access tokens (PATs).
Currently, Mendix only supports [HTTP Basic authentication](#http) and [Windows Authentication](#windows) for Git service providers.

### HTTP Basic Authentication {#http}

With most providers, HTTP basic authentication takes the form of using of personal access tokens (PATs).

To use PAT (or another equivalent), you need to specify it in the **Password** field when Studio Pro requests credentials for the version control server:

Expand All @@ -45,6 +49,13 @@ Currently Mendix keeps PAT using operating system supported solutions:
* For Windows, Mendix uses a credential locker mechanism, accessible to users by using Credential Manager.
* For MacOs, Mendix uses keychains, accessible to users by using Keychain Access.

### Windows Authentication {#windows}

Studio Pro can use Windows Authentication for Git service providers that support it. When you use Windows Authentication, you do not need to provide a password.

You can enable Windows Authentication in [Git Preferences settings](/refguide/preferences-dialog/#enable-windows-authentication).


## Setting Up the Environment

This section describes how to configure a Git versioned app in Studio Pro. You need a Git server and an initially unversioned Mendix app.
Expand Down