I am using Authority labs API in my rails application for ranking service. I am getting connection refused(2) error when I check in API error list.It shows the error type as Callback Error. Please guide me to fix this.
Related
I'm setting up the Hubspot trigger node in n8n.
I'm working on localhost through docker & using ngrok so I have a https URL for the OAuth callback. When I try to connect to my Hubspot developer account I get the error:
Couldn’t complete the connection
Insufficient scopes were provided. Please contact the app developer.
I have selected all scopes in my developer app & in my private app used via the Hubspot parent account.
Does anyone have any idea what could be the cause of this?
Thanks
I am getting the below error while login with google through Keycloak.
401. That’s an error.
Error: deleted_client
The OAuth client was deleted.
Request Details That’s all we know.
The application you are using has a client id created via google developers console. The client id in question was deleted your going to have to create a new client id and recompile your application.
That is assuming this "keyCloak" is your own application if not then you should contact the developer of the application they have a problem
i am using V2 endpoint as explained here https://azure.microsoft.com/en-us/documentation/articles/active-directory-v2-scopes/ to connect to Microsoft Login. I am getting invalid client error after i sign in. in fiddler i see following error , can someone please help me.
AADSTS70002: Error validating credentials. AADSTS50012: Authentication failed
Trace ID: c62c9e93-f7c9-43fe-b5eb-4a6f9dfe6be0
Correlation ID: c14f259c-3e91-4e51-9f82-8feabd35bf5d
Timestamp: 2016-07-22 21:04:19Z
I was receiving the same error and just removing the last forward slash worked for me. Instead of
https://myapp.com/
I used this
https://myapp.com
and invalid_client error went away. It seems the redirect URLs have to exactly match as configured in AZURE AD.
I've been using Oauth Plugin for LinkedIn authentication with salesforce for a few months now without any issues; today we are seeing this error with no change to our existing code. I verified that the API keys and the scope were correct on the LinkedIn Developer site. Anyone know how to solve this issue?
ERROR:
Failed getting a request token. HTTP Code = 403. Message: Forbidden.
Response Body:
oauth_problem=Scope%20NOT_AUTHORIZED%20%3A%20r_fullprofile%2C%20Scope%20NOT_AUTHORIZED%20%3A%20r_network%2C%20Scope%20NOT_AUTHORIZED%20%3A%20rw_groups%2C%20Scope%20NOT_AUTHORIZED%20%3A%20rw_nus%2C%20Scope%20NOT_AUTHORIZED%20%3A%20w_messages
Endpoint=https://api.linkedin.com/uas/oauth/requestToken?scope=r_fullprofile%20r_emailaddress%20r_network%20r_contactinfo%20rw_nus%20rw_groups%20w_messages, Method=GET]
They have made some changes to the LinkedIn API. Have a look at Developer Program Transition Guide
using of youube api getting this error
Error Domain=com.google.GDataServiceDomain Code=403 "The operation
couldn’t be completed. (com.google.GDataServiceDomain error 403.)"
UserInfo=0x7676020 {Error=NoLinkedYouTubeAccount,
error=NoLinkedYouTubeAccount}
You recieve this error since you are using Service account authentication.
The service account flow supports server-to-server interactions that do not access user information. However, the YouTube Data API does not support this flow. Since there is no way to link a Service Account to a YouTube account, attempts to authorize requests with this flow will generate a NoLinkedYouTubeAccount error.
https://developers.google.com/youtube/v3/guides/authentication
You may try to use another type of authentication, such as server-side or installed application, however user should allow to use his account.
If you want to create an app which will allow different users to add videos to your own channel, than you can try ClientLogin authentication protocol.
Look here for more info https://developers.google.com/youtube/2.0/developers_guide_protocol_clientlogin#ClientLogin_Authentication
This protocol is deprecated but I have not found any way to resolve problem.