Facing an issue with my enterprise account where attaching docs (such as Miro, Lucid) attach successfully the first time to Calendar invites, but subsequent attachments fail.
This works fine with non enterprise account. I have disabled API Control for 3rd Party apps and Google Calendar logs not showing any related logs.
Anyone come across this?
TLDR: adding an app such as Lucid to a Calendar invite. First attachment works, all others fail with no error messages.
Disabled API Control in Enterprise Account
Tested with MIRO, LucidChard and a Custom App. All attach on first invite and fail on others
Checked the Calendar logs
Works perfectly on personal Google Calendar
Related
We are using Firebase Auth on a Cordova app, and using it to handle Google sign in. On web, android, and even on iOS Safari, it works just fine. On our cordova iOS app though, logging in the first time will work fine if it makes you type in your email and password, but, if you go to log in and you get the "Choose an Account" screen on google to pick what email to sign in with, it ends up just loading forever when you pick the account.
Looking at the logs of what is happening, it is just calling https://accounts.google.com/_/signin/oauth and then nothing happens after that. The firebase handler URL is never called. There are no error messages in the console, nor do any of the Google requests returning errors in their responses.
We are using firebase hosting, for our web version, and for the firebase 'authDomain' (which is the same domain we are using for web).
iOS was previously working fine for us, but I'm not sure if it was iOS 16 that started the issue, or changes we made, or changes on Google's end.
Does anyone have any idea what could cause this?
We figured out the issue, it appears a cordova plugin we were using that had gotten upgraded had a bug in the new version that stopped custom url schemes from working. We upgraded again to a version that had the bug fixed and the issue stopped.
Good Morning,
So I am facing a dilemma using Firebase Auth (specifically Google OAuth).
Google seems to have blocked the use of their OAuth when a user access my site via a web-view (for example they have clicked on the link in TikTok and the website has opened within a view in TikTok)
It makes sense as to why Google has blocked this, however, this is now stopping my ads from being successful as users see the ad, click on the link, and then it opens up in the TikTok web view, and then they can't log into my web application.
I'm using the simple Firebase Authentication plugin, with Nuxt/Firebase the code for it is as below:
const provider = new this.$fireModule.auth.GoogleAuthProvider()
provider.setCustomParameters({
prompt: 'select_account'
})
this.$fire.auth.signInWithPopup(provider)
Does anyone know any workaround? I've googled this so much but the only real solution I have come across is if I'm creating an android/ios app and this is not a mobile application, this is just a web application.
Thanks so much for your help.
I was going integrate google login in application.
As i have login into https://console.developers.google.com/ but not able to get my project (which i have created) data for client ID and client secret Key, or other details. I don't know what is happening.
Error, when i search my project name and clicked i get this
Error when, all registered projects are fetched.
As I was on Google Chrome. It was not working, but when i shifted to incognito mode. It works well. Please do hard refresh for well response.
I am using ASP.NET forms (not MVC) along with their out of the box templated solution for logging using Facebook, Twitter, etc (all wrapped up in Microsoft.AspNet.Membership.OpenAuth).
Everything seems to be working fine except for one thing: Every time a user logs in with Twitter, they are being redirected to Twitter and asked to Authorize the application. Regardless of whether they have done it already (i.e. The user logins for first time, authorizes against the Twitter app, get redirected back to our site perfectly. Then they log out, and go to log in again, and they are re-prompted to authorize. The application shows up in the list of approved apps under the user's Twitter account.
I have ready some places where people are having similar problems, but not using the Microsoft libraries. They seem to point to using a different URL when launching to Twitter, however, I don't seem to be able to find that level of granularity with the MS libraries.
Has anyone been able to reproduce/solve this issue using these libraries? I am not intimately familiar with how this all works, but I notice that DotNetOpenAuth is also a part of my references. If this is the library that is feeding the Membership.OpenAuth classes, perhaps there is an update that I need? My DotNetOpenAuth.OAuth version shows 4.1.0.0 and runtime version if v.4.0.30319.
Thanks,
J
I had the same problem. I'm using the following to connect to twitter:
OAuthWebSecurity.RegisterTwitterClient(key, secret)
and using the latest OpenAuth 4.3.0.0
Login works ok, but it keeps asking to Authorize App each time.
Turned out that in my Twitter App settings I did not have the following ticked
Allow this application to be used to Sign in with Twitter
When I ticked this, the normal OAuthWebSecurity.RegisterTwitterClient() worked fine
We are working to integrate one of our client's existing accounting system into Google App. Eventually we need to list it on Google App Marketplace.
Here is what we have already done:
Downloaded the sample .NET app available from Google - this one
Created a vendor profile on the Google Apps Marketplace
Listed our test application on the Google Apps Marketplace
So far we have ONLY been able to authenticate the user using DotNetOpenAuth.
We are struggling with following issues:
Unable to access the Calendar Data API and display the next appointment. We are getting 401 Unauthorized when querying the Calendar Data API.
To access the Calendar Data API we need to have a ConsumerKey & a ConsumerSecret - which is made available ONLY after you submit your application for Approval.
We submitted the app for approval to get a ConsumerKey & a ConsumerSecret although its just a pilot app that we are building first. We don't want that app to be published as of now but we could not find a way to keep that listing private and available ONLY for dev & testing purpose as of now.
We have placed the ConsumerKey & ConsumerSecret in the sample marketplace app but even now we get a 401 Unauthorized access while quering the Calendar Data API.
We have already spent 2-3 days trying to find proper documentation for this and get it to work but in vain. Any help / guidance to get it to work and also keep the listing private in dev mode until we are ready, would be really appreciated.
Here is the modified 2 page source code i am trying to run.
There are some key misconceptions in your post.
Your keys are already available to you. Open Marketplace, click on "My Vendor Profile" top right, and look right under the listing, below the stars: View OAuth Consumer Key link is there. If it isn't, you did not mark your app as an installable one. To fix that, create a new app entry, and make sure you provide a valid manifest.
To test your new app, BEFORE you submit your app for approval, open the Marketplace page for it and click the Add it now button. You will be offered a field to enter the Google Apps domain name to test with.
Only domains you add your app to will be accessible with the marketplace key.
Chances are if you sort these two things out things will start working :)