How can one authenticate, as I am not been able to authenticate - even though I know credentials are correct.
Error which I am facing -
Clone URL is incorrect.
Clone URL requires authorization.
Related
I have a self hosted Gitlab CE with Azure AD authentication enabled. I am able to login to Gitlab, but not able to perform any operations via Git command line. I see below message on the project's home page:
Your account is authenticated with SSO or SAML. To push and pull over HTTPS with Git using this account, you must set a password or set up a Personal Access Token to use instead of a password. For more information, see Clone with HTTPS.
What is the use of having SSO if I need to setup a password to use the Git command line? Or am I missing something obvious?
Is it possible in Azure DevOps to create a "ReadOnly Deploy Token" for a repository?
Practically, to access the repository in a "ReadOnly" mode with a url, eg:
https://deploy:myDeployToken#dev.azure.com/myCompany/myProject/_git/main
We want to link a Private Azure DevOps Repository as a composer repository.
GitLab has such a feature that looks like this:
You'd need to create a personal access token with Code (Read) scope that only has access to that specific repository.
Or register an ssh key for a user that only has read access to that repository.
There are no repository scoped tokens in Azure DevOps that you can easily generate.
What you can do, is kick off a pipeline and steal its token (for the duration of the pipeline), you can set the desired permissions for those. But that's an OAuth token that will expire after a short time.
There should be an API to generate such OAuth tokens, but that's no available from any UI and those tokens have a relatively short life.
Im trying to link my git repo to an azure synapse sandbox and Im facing this error
Failed to list GitHub repositories. Please make sure account name is correct and you have permission to perform the action.
Im using a personal access token, an enterprise git account, and full repo access for the token.
Could someone please point what I maybe missing. Does it require any permission on the azure side as well ?
In the GitHub repository owner, only give the owner name. Eg johny, instead of GitHub.com/johny
Configure a Repository
Go to GitHub -> open code and copy HTTPS Link use this link to GitHub enterprise URL Login on synapse -> Creating a personal access token on GitHub -> connect to GitHub.
Creating a personal access token
Reference:
https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token
https://www.reviewboard.org/docs/manual/dev/admin/configuration/repositories/github-enterprise/
There's a documentation for Azure Pipelines that elaborates what kind of authentications can be done to access GitHub repositories: GitHub App, OAuth and Personal Access Token. (https://learn.microsoft.com/en-us/azure/devops/pipelines/repos/github?view=azure-devops&tabs=yaml#github-app-authentication)
The documentation says that the GitHub App authentication is the "recommended" one but later it does not really turn out why this is the case... E.g. there is one interesting thing that worked with GitHub App authentication: Creating a yaml pipeline where you define a container ACR resource with a "latest" trigger. With the correct ARM Service Connection from the yaml somehow Azure DevOps is creating an Webhook for the specific ACR however if you use PAT it is not the case.
Is there an actual best practice for the authentication type? Or generally a good argument why one is better than the other?
A personal Access Token and an OAuth token link Azure Pipelines to GitHub with your user account. Your access token will be used to download the repo and the pipeline could access the token to access any repository your user has access to. While often convenient, it's a problem since you may not be the only person using the integration, so others could use your credentials by changing the pipeline.
The user bound tokens also have the problem that the owner of that user account may leave the company, breaking all pipelines, or worst, requiring quite a bit of reconfiguration to make sure that user loses all the access to the repositories the pipeline has access to.
The GitHub App will allow you to configure exactly what repositories should be allowed to be accessed by Azure Pipelines. It's decoupled from your user account and the access can be limited to just the repositories you want.
I'm trying to follow the steps layed out in this article: https://blogs.msdn.microsoft.com/visualstudioalm/2016/07/12/jenkins-queue-job-build-task/.
It seems pretty straightforward, but I keep getting invalid login error when trying to queue a build. Right now we are using azure active directory for our jenkins security provider, which I'm assuming is why it might not be working. Does this service only work when using the basic jenkins authentication?
I added my user and pass for azure, but of course they are not working.
Yes, it is caused by the AAD authentication. The work around for this is creating an API Token in Jenkins after login and then use the "User ID" and "API Token" as username and password when you add Jenkins service endpoint in VSTS.