Error SC424 connecting Make.com to google analytics - google-analytics

Ive added a new api app in GCS for GA4 & UA data connection to make.com. I granted credentials and added google analytics scope. The authorised redirect URI I used was https://www.integromat.com/oauth/cb/google/. I keep getting the following error when trying to connect make.com via the OAuth 2.0 module:
{"message":"The request failed due to failure of a previous request.","code":"SC424","suberrors":[{"message":"Account error (invalid_request)","name":"Error"}]}

Related

Getting HTTP OAuth 2.0 to work for google analytics (ga4)

Cant establish persistent API connection to GA4 from Make (formerly Integromat). I use an HTTP OAuth 2.0 connection
I've enabled the Google Analytics Data API v1
In GCS I've created a project, Enabled the above mentioned API with authorized domains integromat.com and make.com and also created an OAuth 2.0 app. The scopes I added was:
https://www.googleapis.com/auth/analytics.readonly
https://www.googleapis.com/auth/analytics
I created credentials for a web app with the Authorized redirect URI’s of
https://www.integromat.com/oauth/cb/oauth2
https://www.integromat.com/oauth/cb/google/
The connection works but only for a short period (I assume the token expires). To try and mitigate this I created a service account. That does not work as I cant find a way to add an authorised URI to a service account. This is the Make error:
Error 400: redirect_uri_mismatch
You can’t sign in to this app because it doesn’t comply with Google’s OAuth 2.0 policy.
If you’re the app developer, register the redirect URI in the Google Cloud Console.
Request details: redirect_uri=https://www.integromat.com/oauth/cb/oauth2
Any ideas please? I’m truly stuck
Your question lacks a bit of information as to what it is exactly you are trying to do. However there is enough here that I can help you clear up a few issues or miss understandings.
Oauth2
Oauth2 allows your application to prompt a user to request permission to access their data. The authorizaton server returns to you an access token, this access token is good for only an hour and then it will expire.
If you are using a server sided programming language then you can request offline access, at which point the authorizaiotn server will return to you an access token and a refresh token. The refresh token can then be used by you when needed to request a new access token.
service accounts.
Service accounts can be used if you are only accessing private data that you the developer own. You can create a service account, then go in the admin section of the google analytics website and add the service account as a user it will then have access to that account. There will be no need to request consent of a user to access the data it will just work. Note: service accounts only work with server sided programming languages.
redirect uri issue.
The redirect uri must exactly match the web page that your application is sending. In this case the error messages says you are missing https://www.integromat.com/oauth/cb/oauth2 you should add that.
Google OAuth2: How the fix redirect_uri_mismatch error. Part 2 server sided web applications.

Registered callback does not match with the provided url in wso2 api manager 3.2.0

I have two server that run in following addresses:
https://172.25.129.66:9443/publisher
https://172.25.129.67:9443/publisher
I faced with following error in wso2 api manager 3.2.0 :
Registered callback does not match with the provided url
And also I configured call back url in carbon as folowing :
regexp=(https://172.25.129.66:9443/publisher/services/auth/callback/login|https://172.25.129.66:9443/publisher/services/auth/callback/logout|https://172.25.129.67:9443/publisher/services/auth/callback/login|https://172.25.129.67:9443/publisher/services/auth/callback/logout)
What is the problem that only https://172.25.129.67:9443/publisher has call back error?
This error might have occurred due to the mismatch of the API Publisher or API Dev portal access URLs and callback URLs which are configured in API Publisher and API Devportal Service Providers.
Please refer https://apim.docs.wso2.com/en/3.2.0/troubleshooting/troubleshooting-invalid-callback-error/#troubleshooting-registered-callback-does-not-match-with-the-provided-url-error to resolve this issue.

Firebase Google Auth: Getting 'The identity provider configuration is disabled' even though it is enabled

I'm getting 'The identity provider configuration is disabled' from Firebase Google Authorization even though it is clearly enabled in the Firebase console. It doesn't happen for all Google accounts.
Is anyone aware of any other reasons why this error message would be the response from the Firebase Authorization server? This is a web-app.

Running Firebase web SDK under phantomjs fails to authenticate valid tokens (auth/network-request-failed)

I am trying to use phantomJS to create a pdf of a authenticated part of a Firebase web app.
The set up is as follows
A cloudFunction is triggered when firestore is updated.
The cloudFunction creates a custom token with admin.auth().createCustomToken with the relevant claims.
A url to the hosted firebaseapp app is created, with the token as a query param.
The URL is given to phantomjs to create a pdf of the page.
When the firebase webapp boots, it grabs the token, and uses firebase.auth().signInWithCustomToken
On success it renders the page.
The hosted page works fine, and I can grab the token that the cloudFunction creates, add it to the URL and test it all in chrome with no issue.
However, when running this under phantomJS, the call to admin.auth().createCustomToken fails with
auth/network-request-failed .
A network error (such as timeout, interrupted connection or unreachable host) has occurred.
I have tried the following
Setting '--ignore-ssl-errors=yes', '--ssl-protocol=tlsv1', '--web-security=false' on PhantomJS
Setting Access-Control-Allow-Origin * on the hosting firebase.json rules
Setting a Content-Security-Policy for all the google apis on the hosting firebase.json rules
Does anyone know what would be blocking the google api within phantom?
Could it be the User agent?

ASP.Net - Google Calendar API V3 redirect_uri_mismatch error

I am getting redirect_uri_mismatch error while getting refresh token using Google Calendar API V3. I have web application, which shows google calendar access consent window to user and if user allow access than i store refresh token received from request to my database. I also have windows service which runs once daily. This service fetch google calendar events for all users who have allowed calendar access into my application. It is working fine in my local environment but gives error on live site.
I have choose Application Type as Other while generating client id and secret. How can i resolved this error on live URL or where can i change redirect uri in Google API Console?
I have both web application and windows service using calendar api so i want same client id and secret needs to be used for both. Generating separate token for application type web application and other for windows service is not an option for me because i have tried that and it throws unauthorized client error while windows service try to fetch calendar events using refresh token generated throw web application client id & secret.
This error indicates that you are using the web redirect flow instead of the recommended flow with JS widget support. The web redirect flow does not take advantage of many features such as Cross-Device Sign-On, Over-the-Air Install, and so on.
This issue is related to the Authorized Redirect URI field settings for the Client ID.
To resolve:
Access your list of credentials in the Google API Console .
From the project drop-down, select your project .
On the Credentials page, look for the list of OAuth 2.0 client IDs, and select the web application client ID. This takes you to a details page.
In the Restrictions section, the Authorized Redirect URI field(s) should contain the appropriate protocol, host name, port, and path information that will receive the redirected flow.
Here's a related SO ticket: Google OAuth 2.0 redirect_uri_mismatch error

Resources