We have a custom Integration for Docusign in Salesforce. A week ago, we changed the password in Docusign. Since then we are not able to access Docusign's API. Below is the Error Message which shows up in Debug Log.
Error: Web service callout failed: WebService returned a SOAP Fault: One or both of Username and Password are invalid. faultcode=soap:Client faultactor=missing in Web.Config
Please advise!
Appreciate your help!
It would appear that the username or password that is being sent to the API is wrong. Try capturing the Callout request is the debug log to see what values are being sent.
Related
I am unable to get token for my api using the set up as shown in the image. As you can see the hashed value does not have a '+'. The unhashed password is 'ecret'. That is not a typo. I have also tried RequirePkce to false. I have turned on logging for identity server but it has only limited information. There is a single message.
Client secret validation failed for client:api.client.
I have also seen SO entry here.
Finally I was able to figure out. The samples are behind the development. Documentation may be little more updated.
While searching for other authorization mechanisms, it occurred to me that HTTP had an authorization header as in the image.
I have been trying to perform a token based authentication (TBA) with netsuite, but keep getting "Invalid Login Attempt"
I tried to refer to this also:
How to request Netsuite RESTlet with TBA authentification
And I tried it both on
python:
https://gist.github.com/axilaris/6ecc58e43895dba17ce0ca1b8ce25d9a
(please check the code and response error)
it was mainly based on https://www.techfino.com/hubfs/Techfino_March2018/Images/Token-Based-Authentication-Guide-for-NetSuite.pdf
and
postman:
Here are my netsuite configuration for the permissions:
"Invalid login attempt" is a generic error thrown by NetSuite when there's something misconfigured in the authentication headers. The best way to troubleshoot this is to use the "Login Audit Trail" search. From there, you should be able to troubleshoot what went wrong with your parameters. It could be that you entered an extra character or blank space into one of your tokens or you’re not generating a new timestamp or nonce.
Follow these steps:
Go to Setup > Users/Roles > User Management > View Login Audit Trail.
Check the Use Advanced Search box.
Click the Results subtab.
Add the following fields: Detail, Token-based Access Token Name, and Token-based Application Name.
Application Name.
Click Submit.
The Detail column displays error messages for any token-based authentication logins with a status of Failure.
After carefully debugging I found out that timestamps for generating request token are taking more time. I changed the time offset with my standard time zone. After syncing time, it worked for me. So even token definitions in NetSuite don't expire, timestamps for generating request tokens must be in time-window with time in the NetSuite environment.
Also Check these points:
Doesn't have the Web Services Only Role checked.
Check that your related integration has the TOKEN-BASED AUTHENTICATION checked.
Try switching from HMAC-SHA1 to HMAC-SHA256 for your signature method. NetSuite is ending support for SHA1 and I already had an issue with it once.
I am currently trying to implement the paypal api to get the details of an order, but it shows me the following error:
Uncaught PayPalHttp\HttpException: {"error":"invalid_client","error_description":"Client Authentication failed"} in vendor/paypal/paypalhttp/lib/PayPalHttp/HttpClient.php on line 215
I am using the data that paypal gives me of the client id and the secret that is checked in: https://developer.paypal.com/developer/applications/ following the official documentation, after i set up my server to make calls to PayPal, im currently following this guide: https://developer.paypal.com/docs/checkout/reference/server-integration/get-transaction/
I've been trying to find the solution for two days without much success, do you know why paypal marks this error?
As a note, I am still in sandbox (the client and the secret are from the sandbox too) and I am using the default application created by paypal, does it have something to do with it?
It appears the request for an access token is failing, but we cannot comment specifically without seeing a full request+response log added to your question's details.
Ensure you are connecting to api(-m).sandbox.paypal.com with HTTP basic authentication ("Authentication: Basic ..." header) that has a base64 encoded clientid:secret of a Sandbox REST API app, and that the POST data is grant_type=client_credentials
Documentation: https://developer.paypal.com/docs/api/overview/#get-credentials
I have successfully configured a service provider in Wso2 Identity server. With Oauth2 as inbound authentication method. I am facing some issue in Access Token Expiry time. I debugged the issue by following steps
Using Generate Token API - https://localhost:9443/oauth2/token - i got generated access token as response.
data{"token_type":"bearer","expires_in":3600,"refresh_token":"a0e09620d3185a6f7dc2cd42f092e76c","access_token":"b2267f60892c6c94f58a421d2d529a"}
In above response the expiry time is 3600. which is same as configured in identity.xml. But When I use this access_token in OAuth2TokenValidation.validate SOAP service, the expiry time is completely doubled as 360000.
I have test this in soap UI tool. I have attached a screen shot of it.
Is there anything, i am missing from configuration side or some issue at calculation of expiry time at OAuth2TokenValidation validation soap api. Need help to resolve this issue.
Thanks
You can change the value on $IS_HOME/reposotory/conf/identity.xml file.
The tag is <AuthorizationContextTTL>15</AuthorizationContextTTL>. And, the default value is 15.
I logged into the API explorer and authorized my dummy company file here: http://idsapiexplorer.cloudapp.net/V2QBD#api
It is indicating everything is ok:
When I try to make a request, I keep getting the following response:
Here is the ErrorDesc:
<ErrorDesc>message=Exception authenticating OAuth; errorCode=003200; statusCode=401; source=OAuthStrategy; oauth_problem=token_rejected; cause=net.oauth.OAuthProblemException: token_rejected</ErrorDesc>
I'm guessing I'm probably not using this correctly. Is there any more documentation I can read to learn? Or is there an actual problem happening that is causing this error? Any help is appreciated.
The error means the token was not found, expired or invalid.
I would try refreshing your access token and you should be all set.
thanks
Jarred