Azure DevOps Artifacts 401 error when publishing npm extension - npm

I'm trying to get Azure DevOps Artifacts service up and running. I can get it to work with the 90-day token generated by DevOps but not with a custom PAT generated by my account Security panel. It just gives me a 401 error. I followed the instructions for the PAT from here: PAT instructions
My registry url is https://pkgs.dev.azure.com/mycompany/_packaging/packages/npm/registry/
My extension .npmrc file is like this:
registry=https://pkgs.dev.azure.com/mycompany/_packaging/packages/npm/registry/
always-auth=true
My system .npmrc is like this:
//registry.npmjs.org/:_authToken=xxxxxxxxxxxxxxxxxxxxxxxx
//pkgs.dev.azure.com/mycompany/_packaging/packages/npm/registry/:username=mycompany
//pkgs.dev.azure.com/mycompany/_packaging/packages/npm/registry/:_password=xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
//pkgs.dev.azure.com/mycompany/_packaging/packages/npm/registry/:email=devservices#mycompany.ca
//pkgs.dev.azure.com/mycompany/_packaging/packages/npm/registry/:always-auth=true
If it helps, here's the settings I used to generate the PAT:
Any guesses where I might be going wrong?

Any guesses where I might be going wrong?
Please have a try to generate a PAT with a narrow scope of "Packaging (read and write), not build permission. You could click the [show all scopes] to find it.
For more information, please refer to set up your npmrc files

Related

Clone failed: missing OAuth configuration (GitLab, PhpStorm)

After deactivating my antivirus I could clone repositories without problem, but I have a problem with private ones. When cloning and setting up my credentials they're not accepted and I get the following message:
Clone failed, warning: missing OAuth configuration for...
I’ve checked with the administrator and he says all is working from his side.
What could be the problem? Do I need to go through all the OAuth process? The administrator said that it is not necessary and has something to do with my computer.
Any help will be appreciated.

Logon failed, use Ctrl + C to cancel basic credential prompt

I'm facing problems while trying to pull/push my code into a GitHub repository using the cmd prompt for the last two days. How can I resolve this issue?
Logon failed, use Ctrl + C to cancel basic credential prompt. Username for 'https://github.com': satyendrasingh8 Password for 'https://satyendrasingh8#github.com': remote: Invalid username or password. fatal: Authentication failed for 'https://github.com/satyendrasingh8/chatApp.git/'
Fitz_Hoo is right! I just wanted to give a more detailed explanation that fix my issue. Essentially GitHub deprecated their password authentication recently (you can read more by clicking here).
Now instead of adding your username/email and password, you will login with your browser. The image below is the new interface. As Fitz_hoo mentions, you must update your Git to see the new changes!
If you are using Windows, you can simply use this command below to update your Git:
git update-git-for-windows
I fixed the problem just simply by upgrading my client Git Bash to the latest version!
When I encountered the problem, I received an email from a GitHub official, who told me the reason was mainly the Git version was incompatible:
GitHub has changed how users authenticate when using Git for Windows, and now requires the use of a web browser to authenticate to GitHub. To be able to login via web browser, users need to update to the latest version of Git for Windows. You can download the latest version at:
https://gitforwindows.org/
One reason for this message could be that the remote branch you were trying to pull was already deleted.
Delete the GitHub entry from Credential Manager: Control Panel → User Accounts → Credential Manager.
Then push the code again.
For me, the problem was that instead of my username I was trying to login with my email.
I received an email from GitHub telling me
We recently updated the format of our API authentication tokens,
providing additional security benefits to all our customers. In order
to benefit from this new format, please regenerate your personal
access token
I regenerated my personal access token (PAT) and was then unable to log in from command line on Windows 10 when I tried something like git pull.
A window would pop up, inviting me to enter 'username or email' and password. I tried various combinations, using the PAT, as mentioned in the GitHub documentation, and the actual password, but every time I received:
Logon failed, use ctrl+c to cancel basic credential prompt
Thanks to the answers from Fitz_Hoo and ousecTic, I updated my Git install with the command provided by ousecTic, and the authentication process was then completely different.
You can opt to use a PAT, but when you paste it in, no characters at all are shown, so just hit Enter.
In my case, I had this issue in relation to the federated authentication to AWS CodeCommit. The fix was to upgrade git to +v2.30.z (i.e. 2.35.3) and disable interactive prompt (docs):
git config --global credential.interactive false
A global configuration in ~/.gitconfig would look like:
[credential]
interactive = false
A AWS CodeCommit specific configuration, would look like (in ~/.gitconfig):
[credential "https://git-codecommit.us-east-1.amazonaws.com"]
interactive = false
here is the solution which works for me, uninstall Git from Machine after that install new version of it and sign in via web

How to re-download Vault Credentials

One of my backups has failed because seemingly the pass phase is corrupted.
I am attempting to re-register the server (I do not know if this will fix the problem but I do know that in this process the pass phrase is entered) and so need to re-download the Vault Credentials.
In the old Azure portal the download of the Vault Credentials link was right there as soon as you went to the particular vault.
In the new Azure portal I cannot find it anywhere. I have looked and looked and Googled and Googled.
I get the feeling that one has to start the whole backup setup again for the server in order to get the credentials via Getting Started > Backup.
So I am in vault that the server backs up to and I go to Getting Started > Backup and follow the steps and then I end up with a list of servers that I need to choose from but my server is not there because it says "VMs in same region as vault and not protected by another vault are shown....".
Anyway I am stuck.
Path to download the vault credential file: Home>Recovery Services vaults>Select your recovery services vault>Properties>Backup credentials
See the screenshot:
OK I fixed my problem but I did not resolve the "How to re-download Vault Credentials".
In the Azure Backup app on the server I went to Actions > Change Properties and re-entered the pass phrase and tried to save it.
I got a message that nothing was saved because the pass phrase had not changed.
So how the heck did it know that if my initial problem was that the pass phrase was corrupted???
I chanced my luck and tried a "Backup Now" and lo and behold it worked.
GO FIGURE AND THANK YOU TEAM AT MS FOR YET ANOTHER CONUNDRUM I HAD TO SOLVE WITH SMOKE AND MIRRORS.
Don't get me started...

GitHub integration error "cannot verify team membership"

I have launched a drone/drone:0.8 using docker, and providing these environment variables:
DRONE_ADMIN=stevecrozz
DRONE_GITHUB=true
DRONE_GITHUB_CLIENT=...
DRONE_GITHUB_SECRET=...
DRONE_OPEN=true
DRONE_ORGS=myorg
When I attempt to log in, I get:
msg="cannot verify team membership for ."
I was expecting to be logged in since I am a member of 'myorg' on github. It isn't clear to me what I can do to troubleshoot from here.
In this case, it turned out that the Github OAuth application had not yet been approved by 'myorg' on Github. Once an administrator approved the application, I was able to successfully log into my drone application and use it.

Openshift Origin Latest Project creation issue

I am unable to create project in open shift. I created a project previously and deleted it. Looks like a project exists but unable to access or delete it. Seems like i am stuck. Also logging into the console https://console.preview.openshift.com/console/ doesn't show any existing projects.
I ran the following oc commands from the terminal.
Any suggestions on how to resolve this issue?
Thanks
XX:~ XX$ oc new-project test
Error from server: projectrequests "test" is forbidden: user XX cannot create more than 1 project(s).
XX:~ XX$ oc delete project test
Error from server: User "XX" cannot delete projects in project "test"
XX:~ XX$ oc status
Error from server: User "XX" cannot get projects in project "default"
XX:~ XX$ oc get projects
You need to give privileges/policies to your user which will allow the actions you want to perform.
If you are just in a proof-of-concept environment I would recommend the make your user cluster-admin in the whole cluster. This will give all the possible privileges to your user. Of course this in't recommended for every user in a 'real' environment.
First you need to authenticate with the 'default admin' which is created after the installation. This default admin-user isn't working with the normal user/password authentication. It's using a client certificate.
oc login -u system:admin --config=/etc/origin/master/admin.kubeconfig
Now you will see a list of the available projects (default, openshift management, etc). Now you're able to give cluster-roles to other users.
Make your user cluster-admin over the whole cluster
oadm policy add-cluster-role-to-user cluster-admin (youruser)
Now you have the cluster-admin privileges inside the whole cluster. You are also able to give privileges for some user in a specific project and not in the whole cluster. Than you have to use:
oadm policy add-role-to-user <role> <username> (in the current project)
This will give the role to a user, but only inside the project from where you've performed this command.
For more information about the avaiable cluster roles and policies I will point to the official documentation.
I raised a defect with Openshift Team as pointed out in the Support Link.
https://docs.openshift.com/online/getting_started/devpreview_faq.html#devpreview-faq-support
Here is the response i received from Support Team.
It seems that you have issued a bug and followed up for this already:
https://bugzilla.redhat.com/show_bug.cgi?id=1368862
After the cause is investigated, our operations team will sure clean up the project manually for you to allow you continue working with the developer preview
Latest update:
The project has now been cleaned up and you should be able to create a new project.
I am able to create Project in Openshift now.