I am sending my data from firestore to algolia. Before sending that I have to set that data from firestore to google cloud platform. For that I ran following commands on google cloud shell terminal:
firebase login
Then it gave me this messsage:
Firebase optionally collects CLI usage and error reporting information to help improve our products. Data is collected in accordance with Google's privacy policy (https://policies.google.com/privacy) and is not used to identify you.
Then it asked for Allow Firebase to collect CLI usage and error reporting information?. I replied yes. Then it gave me a link to authenticate the account. After clicking on that link, it gave an error message.
This is the error message which I recieved
How to resolve this error? I tried many tutorials but could not find any solution. i tried this link.
https://developers.google.com/identity/protocols/oauth2/web-server#handlingtheresponse
Well, This is happened on my side as well.
When the link has been displayed in console part of it wasn't detected by the terminal application. As the result it opened in web browser just as a part of the link. If analyze whole link you will see that near the end of the link there is something like response_type=. If this part is missing this error massage is shown.
I hope it will help!
Related
This question already has answers here:
Heroku and GitHub: "Items could not be retrieved, Internal server error"
(12 answers)
Closed 9 months ago.
When I try to add GitHub as my deployment method, it just pops up ands says one of these two things. Error1(image)
Error 2(image)
But the really odd part is that when I look on GitHub it shows Heroku as a OAuth application that is added but says it was never used. And then, in logs it says things like this:
Error logs
Does anyone know what's going on? I'm using Heroku to host a discord bot and ever since I logged out of GitHub on Heroku because it was acting up I cant get back in.
deploy from github is currently unavailable due to some hacker attack
reference: https://status.heroku.com/incidents/2413
We are dedicated to ensuring the security of our customers, and as
such, continue to pursue all potential leads as part of our
investigation. As part of that commitment, we want to let you know
about two additional findings that may impact a small number of our
customers.
As reported on status.heroku.com, on April 7, 2022, a threat actor
obtained access to a Heroku database and downloaded stored customer
GitHub integration OAuth tokens. On that same day, the threat actor
downloaded data from another database that stores pipeline-level
config vars for Review Apps and Heroku CI. Additionally, another small
subset of Heroku users had their Heroku tokens exposed in a config var
for a pipeline. This was identified on May 16, 2022, after further
forensic investigation. We have no evidence of any unauthorized access
to Heroku systems since April 14, 2022.
Any users affected by these issues were notified directly and provided
with additional guidance. If you did not receive an email directly
from us, we have no evidence that you were impacted by either of these
recently identified issues. If you received an email from Salesforce
(techcomms#mail.salesforce.com) and have identified suspicious
activity, please contact security#salesforce.com.
For an update on our current progress with regards to the GitHub
integration, please see this blog post.
so you can deploy manually through heroku CLI
as #MarcoWriteCode has mentioned the basis of the error that you are facing.
I would suggest that you go through the Heroku CLI documentation and continue your deployment from here. https://devcenter.heroku.com/articles/getting-started-with-nodejs
Use heroku CLI for a bit, then switch back to github deploys
I'm currently working on an application for myself in which I need access to my own photos/albums on Google Photos. I have gotten by using the oauth 2.0 token generated in the playground, but I'd like to get a more permanent solution that does not require me manually regenerating the token. Is this possible with Google Cloud? The app is meant to run in daemon, so this makes any option with consent pages unusable. The scopes I'm using are:
https://www.googleapis.com/auth/photoslibrary.sharing
https://www.googleapis.com/auth/photoslibrary.readonly.appcreateddata
https://www.googleapis.com/auth/photoslibrary.readonly
I have tried using the https://accounts.google.com/o/oauth2/token and https://accounts.google.com/o/oauth2/auth endpoints to generate one programatically, but the only minor success I had was /auth sending me to a consent screen. I've also looked at using the refresh token given by Google Oauth playground with no luck there either.
Just looking to see if there is anything that I am missing.. This is my first post on stackoverflow, so please let me know if you need any more information.
I was unable to make it an internal app as it was for personal use and not for an organization.
Solved this by first using the google api package to create my own access/refresh token for my oauth client, then calling the https://oauth2.googleapis.com/token endpoint each time to generate a valid access token. I hope this can be helpful to someone else!
According to the setup documentation, as long as your app is marked as internal, you should not need to verify the app and can use it without the consent screen.
I built an integration with the DocuSign API in the sandbox environment and it is ready to move to production. We purchased the Basic API package this morning only to find that we can't set dataLabels in our template creation page. The attributes pane on the right just doesn't have the dataLabel field on it. I'm here to try to find out why. Without the dataLabel, we can't pre-fill data before sending it for signing as far as I know. I've logged out and logged back in to the admin console. I've confirmed it shows our Basic API package.
P.S. I understand this has nothing to do with actual code. I attempted to get help from a DocuSign live chat rep and he wouldn't give me anything but a canned response to come here and submit a ticket and refused to give me anything else.
I went through the live chat again with a different rep and we got it sorted out. Turns out they have to send you an email and you have to "enable" that feature through the email or they won't show up.
I got the error when trying to get an access key for one of our APIs.
"AADSTS65001: The user or administrator has not consented to use the application with ID '{GUID}'
First, I was trying to prompt=consent during login, thinking that I had new consents that weren't prompted during login. And I got the following error.
"AADSTS65005: The application '{GUID}' asked for permissions to access a resource that has been removed or is no longer available. Contact the app vendor."
I removed prompt=consent and started fiddling with the permissions in Azure, and now I was stuck on the same error.
I changed everything as it was, but I still get the error. However, this only happens to my user. Everyone else can still log in without problems.
So my problem is actually in two parts:
The first error when trying to get an access token for the API.
Somehow I need to prompt the user with consent, but I am using adal.js which uses a silent retrieval of the keys using an invisible iframe. I want the support to be when the user logs into the web app.
Is this possible?
My user can't log in to our web app anymore. Everyone else can. Did anyone encounter this before?
The product is a SPA Web App written in React, and we use adal.js (adal-vanilla) as a library for authentication to Azure AD.
Update
I finally got some stuff working. Not all the way, but at least it's a start.
The problem with this is that users registered on other tenants (this is a multi-tenant app) don't get consent to use the API. These users get the error. However, I registered a user on the same tenant, and everything worked as intended.
Problem two was solved by removing all the permissions, adding them one by one, and testing in between. Somehow this worked after two-three tries.
The problem is that users from other tenants don't get a consent prompt to access the API.
Somehow the issue got fixed, I'm not 100% sure how or why but here are the steps I performed to fix it if someone finds themselves in a similar situation:
Ensure that all permissions are correct (APIs are added as delegated permissions to the client)
All services (web app & apis) are multitenant
Update manifest with:
"availableToOtherTenants": true,
"knownClientApplications": [
"{client app application id}"
],
(availableToOtherTenants was false for the API even though it was marked as multitenant in the settings)
The consent might be possible to fix with prompt=admin_consent.
As for the second problem, you can add your web app as a known client application of the API. This will allow simultaneous consent when the user authenticates to the web app.
To do that, find the API app registration in Azure Portal's Azure AD blade. Then open its manifest (there is a Manifest button on the app blade). In there should be a "knownClientApplications" property. Add the client id of the web app in the array and save the manifest.
E.g.:
"knownClientApplications": [
"bda6ffff-ffff-ffff-ffff-ffff8bf8c57f"
],
Firebase keeps giving me empty "" instead of generating a URL for "storageBucket" when I try to get the code to paste into my HTML for login through Google. I am assuming this is the reason I am getting the error: This domain is not authorized for OAuth operations for your Firebase project. Edit the list of authorized domains from the Firebase console.(anonymous function) # iframe.js:84
I am using browser sync to user localhost which is supposed to be an authorized domain. I have the firebase cdn in my header of my HTML and everything that was generated for my firebase app (except for the storageBucket). I tried importing my app to the new Firebase, just typing in my app name in a similar storage bucket URL ("eventSpot.appspot.com") and I tried just creating a new app in Firebase. None of these worked. Is there something I am missing?
Thanks in advance for your help! :)
The storage tab can take some time just after project creation - but if you've left it a little while and you're still getting the error, it may be some APIs have not been enabled.
Can you go to https://console.developers.google.com/project/_/apis/enabled
Check for:
App Engine Admin API
Google Cloud Storage
Google Cloud Storage JSON API
If any aren't enabled, enable them. After that, try the storage console again.