On version 1.1 of the Twitter API, we could use "account/verify_credentials".
However this now requires Elevated access to use the 1.1 version of the API.
Is there a way todo it using the V2 part of the Twitter API?
Edit: all I need is the username
At the moment, there is not a way to do this in v2. However, a future API feature may add this (probably as part of the OAuth 2.0 user implementation that is currently being worked on).
You can request elevated access to get to v1.1 endpoints for free.
Related
I think in 2020 Google announced that they would be turning off access to LSA apps. That you need to use OAuth to access their services.
https://workspaceupdates.googleblog.com/2020/03/less-secure-app-turn-off-suspended.html
Our application uses IMAP/SMTP/POP3 however to use these with oauth we need the full gmail scope ie (https://mail.google.com/). When we tried to get verified we were denied.
So we started building a gmail client using the gmail api with a more granular scope. however the docs themselves say to not use the api if you're making a client. https://developers.google.com/gmail/api/guides
screenshot
Is the correct approach to use IMAP/SMTP/POP3 libraries?
I am trying to integrate quickbooks online v3 with c#.
In earlier version I could connect with appid and token.
Current version I would like to bypass the login and use API. Token is generated after logging in to qbsite.
No, this isn't possible (for what should be very, very obvious security reasons - why would anyone want to allow any person access to all of their companies financial data without any sort of login/authentication mechanism what-so-ever?).
The new v3 APIs use OAuth for authentication. The end-user is required to log in once to generate the OAuth tokens and authorize your app to access QuickBooks data.
After that authorization, you can use those tokens to access QuickBooks data any time you want.
This pretty much exactly mirrors the old qbXML connection ticket method that was previously available.
I have been playing with the new Admin SDK in conjunction with the "upgraded authorisation experience" and wondered if someone has and experience/examples on how to use it. From what I have read, if you upgrade the authorisation experience you shouldn't need to use OAuth 2.0 and get a client ID and secret from the API console.
When you upgrade the authorisation, the API console entry is automatically created so you just have to turn on Admin SDK. Your app should then run simply using your own admin credentials.
Have I misunderstood this and if so, what is the benefit of the new authorisation experience?
I can use the Admin SDK just fine if I create a client ID and secret in the API console but this is using OAuth 2.0 then.
If someone has an example of how to use the admin sdk with OAuth 1.0 i could have a look at it would be much appreciated.
You will still need get your tokens and API key...
Take from the Directory API documentation:
If your application has certain unusual authorization requirements, such as logging in at the same time as requesting data access (hybrid) or domain-wide delegation of authority (2LO), then you cannot currently use OAuth 2.0 tokens. In such cases, you must instead use OAuth 1.0 tokens and an API key. You can find your application's API key in the Google APIs Console, in the Simple API Access section of the API Access pane.
If you are looking for an oAuth2 example with GAS, Arun has a nice example he posted on GitHub, see the SO posting: How to authorize with oauth 2.0 from appscript to Google APIs?
Sorry, I don't have any oAuth1 example to interface with the new APIs.
I'm working on an app and a part of it is to get the mentions count of this app. I created an app on Twitter and I generated an OAuth signature for the REST API v1.1 GET statuses/mentions_timeline and access the mentions timeline to get the count (https://api.twitter.com/1.1/statuses/mentions_timeline.json). My question is how did we dynamically generate the oauth signature to access the mentions timeline and get the counts.
You can either write your own OAuth provider or use an existing library. Here's a list of 3rd party libraries on the Twitter site:
https://dev.twitter.com/docs/twitter-libraries#dotnet
DotNetOpenAuth is good and there are others.
If you want to write your own, check out Twitter's OAuth documentation:
https://dev.twitter.com/docs/auth/oauth
and here's another good OAuth reference:
http://hueniverse.com/oauth/
The OAuth implementation does not change with the new (controversial) Twitter API. You can keep on generating OAuth signatures just like you did with Twitter API 1.0.
What is the preferred method of accessing the Gmail API across sessions without user input? E.g. user logs in once, some fairly-non-sensitive ID is stored on my server, and I use that ID along with my app's secret/key to access user's mailbox...
I noticed that OAuth 1.0 is now deprecated by google (I'm assuming that OAuth 1.0 enables the aforementioned login mechanism), so what should we use? Does OAuth 2.0 + IMAP work with Gmail?
I'm using a Rails 3.2.6 backend.
Without storing the user's password, the only way for full GMail access is using IMAP/SMTP with OAuth 1. With OAuth 2 you currently can only access the Atom Inbox Feed.
Though OAuth 1 was already marked deprecated by Google, it should be supported until April 2015.
UPDATE:
OAuth 2 authorization support for GMail IMAP/SMTP just recently arrived, so this is now the recommended way to go.
I don't find any information in the oAuth API docs about oAuth 1.0 being deprecated.
However oAuth 2.0 seems to be there as well for Gmail: oAuth 2.0 Playground.