GIT extension 2.5.2 does not save token

[Duarte N]

Username:

TITLE

GIT extension 2.5.2 does not save token

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian v18.0.60_build20240329.08 os_Windows 2012/2016/2019/2022

PROBLEM DESCRIPTION

When configuring a GIT repository with the PAT (personal access token) specified in the URL, the token is not stored in the config file (for example: D:\vhosts\domain.com\git\test.domain.com)

STEPS TO REPRODUCE

1. Open GIT extension
2. Click Add Repository from Azure Devops
3. Configure Repository URL with the token (ex: https://<TOKEN>@dev.azure.com/something-com/something/_git/somethingsomething)
4. Connection fails with following error:
Deploying files to test.domain.com
gitmng failed: Cloning into bare repository 'D:\vhosts\domain.com\git\test.domain.com'...
fatal: Verification code expired before contacting the server
bash: line 1: /dev/tty: No such device or address
error: failed to execute prompt script (exit code 1)
fatal: could not read Username for 'https://dev.azure.com/something-com/something/_git/somethingsomething': No such file or directory (Error code 128)

ACTUAL RESULT

The connection is not successfully established because it is done without the token, the repository is not created and the GIT folder configuration is deleted.

EXPECTED RESULT

Connection established, repository created, GIT folder with configuration created and maintained.

ANY ADDITIONAL INFORMATION

This anomaly does not happen with GIT extension 2.5.1

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug

 

[Kaspar@Plesk]

I apologize for the delayed response on your bug report. I tried to replicate your issue, but I ran into some questions. Can you help me clarify some steps?

• In your 2nd step you mention "Add Repository from Azure Devops". However there is no option to specifically add a repository from Azure Devops. Can you clarify what you did here?
• When adding an URL to a repository with a PAT in the format https://<PAT>@dev.azure.com/something-com/something/_git/somethingsomething the PAT gets striped from the URL when adding it to Plesk. Isn't that the case for you?

 

[Duarte N]

Hi Kaspar,

I specified what the repository was because it might be relevant, but we actually just added the repository.

Yes, the token is removed from the repository URL in the Plesk GUI.
But with the new version we noticed that the token it is not created/stored in the configuration file (for example: D:\vhosts\domain.com\git\test. domain.com).

 

[Kaspar@Plesk]

Thank you for clarifying. Much apricated!

If I understand correctly the actual issue is that the token gets stripped from the URL and as consequence does not get stored in the git configuration file. Would that be an arcuate summery of the issue?

 

[Duarte N]

Yes:
- In version 2.5.1 the token gets stripped form the URL and is saved in the git configuration file.
- In version 2.5.2 the token gets stripped form the URL and is not saved in the git configuration file.

 

[Kaspar@Plesk]

Gotcha, thank you! Summitted reported bug for evaluation by developers with ID PPS-15967.

 

[Kaspar@Plesk]

The issue has been recognized as a product issue and can be tracked with EXTGIT-337 on the Plesk change log page. However because this a edge case the issue isn't prioritized. If you need assistance on a workaround for this issue please contact Plesk support for help.