401: Sorry, your credentials are not valid for this resource - coverity

When i click view defect button, i'm getting this page error:
401: Unauthorized
Sorry, your credentials are not valid for this resource.
I'm sign in with my github account. So my coverity email and github email is same. But still i can't look my defects.
Note: I'm owner of my project.

I solved the problem by contacting the coverity scan mail address. it's a systemic problem.
mail: scan-admin#coverity.com

Related

GitHub device verification email not received

After reinstalling windows on my machine, i have tried to login to my Github account using the same user-name password stored in the browser with my Microsoft account...
with Sign in to GitHub
Username or email address page:
its seems to accept the credentials (tried with email as well with username) and then navigate to the next page saying:
Device verification code
We just sent your authentication code via email to y**************#hotmail.com.
But I never receive any email!!!
not in inbox or junk email beside the GitHub Community Summary..
i am afraid to try the Forgot password option - because perhaps it get the auth issue even worse.
Resetting the password seems to be a solution.
The email should arrive within a few minutes in case of setting a new password, even if you had problems in the authentication process.

Github pat token not working while pushing to repo

We are using github private repo in my organization. we have pat token to repo with this pat token i can able to clone but i can't able to push my changes to github with this pat i was below error
git push https://pat:XXXXXXXXXXXXXXXXXXXXXXXX#github.com/companyname/helloworld.git HEAD:featurebranch -f
remote: You must verify your email address.
remote: See https://github.com/settings/emails.
fatal: unable to access 'https://pat:pat:XXXXXXXXXXXXXXXXXXXXXXXX#github.com/companyname/helloworld.git/': The requested URL returned error: 403
This message means that you must verify your email address by visiting the link provided and following the steps to verify your email.
GitHub requires this because it's easy to do but relatively effective at preventing spam and abuse, and it also means that if there ends up being a problem (e.g., your account ends up getting compromised or it's associated with excessive use), there's a way to contact you.
This is required in order to continue and even though your PAT is correct, you won't be able to push until your email is verified.

Why does the PayPal API not recognize my client id and secret

The Paypal API doesn't recognize my Client ID and Secret I got from https://developer.paypal.com/developer/applications/
I wanted to include a server side checkout according to this tutorial https://developer.paypal.com/docs/archive/checkout/how-to/server-integration/
When I do the request to https://api-m.paypal.com/v1/payments/payment I always get a 401 Error with the message "Authentication failed due to invalid authentication credentials or a missing Authorization header.".
I checked multiple times if my credentials were correctly included into the request. I also tested the endpoint in my server environment and as well via Postman.
I also tried the route https://api-m.sandbox.paypal.com/v1/oauth2/token to exchange my credentials with an access token and got the same problem.
I also tried to create multiple Sandbox and Live Accounts and always got the same error.
Has anyone an idea what the problem could be?
There are two separate issues here.
You first need to use /v1/oauth2/token to obtain an access token, and then use that access token to call any of the other actual APIs.
The credentials you obtain from PayPal Developer will be for either "Sandbox", or "Live". Make sure you choose the correct tab (sandbox, for development). Sandbox credentials will only work for api-m.sandbox.paypal.com , and Live credentials will only work for api-m.paypal.com . The two environments are completely separate.
If you still have issues, post the SANDBOX client ID and secret you are using, and the full request and response to the api-m.sandbox.paypal.com endpoint. There should be a PayPal-Debug-Id in any error response, in the headers if nowhere else.

Github Apps: Authorize & Request on applications doesn't return code parameter

I've created a Github app with the option "Request user authorization (OAuth) during installation".
When a user requests his admin to install the app, the admin accepts and gets back to the app. I then get a url like:
http://localhost:3000/auth/github/callback?code=a22757013d09ccc5f6ed&installation_id=18334019&setup_action=install&state=MYAPPSTATE
BUT when the user Authorize & Request and he gets back to the app I only get a url like so:
http://localhost:3000/auth/github/callback?setup_action=request&state=MYAPPSTATE
My question is, how to get Github to give me the code parameter so I can know which user has requested to install the github app ?
Thank you 🙏
Apparently this has been fixed now https://github.com/pre-commit-ci/issues/issues/70#issuecomment-899129055
Here is the response I got from GitHub support:
The code parameter is only returned for authorization during installation. There isn't a way to generate one for the user who has requested an admin to approve, authorise and install.
As an organization owner/admin, you should see on the GitHub App review install page the user who has made this request during the application installation. You can also check the integration_installation_request.create logs in the organization to find the user who has requested the installation

How to use visual studio code with github and 2FA

Our organisation required us to add 2FA to github. Unfortunately,
now we cant commit our work in visual studio code. VSCode prompts for username and password. It doesnt know about 2FA.
There are some very old posts saying to use a personal access token (PAT), e.g.
https://colinmackay.scot/2015/07/15/two-factor-authentication-with-github-and-visual-studio-2013/comment-page-1/#comment-29984
http://www.anilsezer.com/connecting-github-from-visual-studio-after-twofactor-authentication-enabled
However, this does not work either.
The first article says enter the PAT as the username and leave the password blank in the VSCode github login dialog. This does not work as you cant sumbmit with a blank password. Entering a random password gives
Fatal: HttpRequestException encountered.
An error occurred while sending the request.
fatal: HttpRequestException encountered.
An error occurred while sending the request.
remote: Invalid username or password.
fatal: Authentication failed for 'https://github.com/xxx/xxx.git/'
The second article says to use your user/email as the username, and enter the PAT as the password. This is also what the VSCode documentation says. Tired this too, same problem.
Anyone got this working?
Also, does anyone know which of the "scopes" is required for VSCode? I just ticked "repo". Could this be the problem, are more required?
I would advise you can use Personal access tokens.
Just click on your profile picture on the site https://github.com/ (after login), then on Settings > Personal access tokens > Generate new token. Follow the wizard to select what to grant, at least you'll need repo.
On VS Code you provide your usual user name and for password you provide the newly generated PAT.