access-token

Facebook Oauth Access Token Different when using Graph API Explorer

左心房为你撑大大i 提交于 2019-12-03 12:23:36
问题 (Disclaimer: The access_tokens and appIds in this post are fake and are just intended to look real) I'm trying to generate an access_token using the call to the following: https://graph.facebook.com/oauth/access_token?grant_type=client_credentials&client_id=123456789000000&client_secret=03252f2ff1eddffe234a0dc7256abb8c That gives me an access_token in this format: access_token=123456789000000|TR528Smvi4AXMM21Zhmi5XmJwmk If I try to access a fan page that's protected with that token like this

Securely storing an access token

孤者浪人 提交于 2019-12-03 11:05:39
What security measures should I put in place to ensure that, were my database to be compromised, long-life access tokens could not be stolen? A long-life access token is as good as a username and password for a particular service, but from talking to others it seems most (myself included) store access tokens in plain text. This seems to be to be just as bad as storing a password in plain text. Obviously one cannot salt & hash the token. Ideally I'd want to encrypt them, but I'm unsure of the best way to do this, especially on an open source project. I imagine the answer to this question is

Facebook app (NOT user) access token expiration

ぐ巨炮叔叔 提交于 2019-12-03 10:08:41
Do Facebook APP access tokens expire? These tokens are different than the USER tokens; they are acquired like this: https://graph.facebook.com/oauth/access_token?grant_type=client_credentials&client_id={0}&client_secret={1}) as described in the App Login section of the document at http://developers.facebook.com/docs/authentication/ . Are there any circumstances under which they will become invalid? NB: This is NOT a question about USER access tokens (which are clearly documented). There was an identical question http://facebook.stackoverflow.com/questions/7322063/does-app-login-access-token

OAuth 2.0 Generating Token and Secret Token [closed]

血红的双手。 提交于 2019-12-03 10:05:10
问题 It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. Closed 6 years ago . I am implementing the OAuth 2.0 provider server using Apache Oltu framework, looking for some idea on how to generate the access token and secret tokens in java. Please advise. 回答1: OAuth 2.0 specification doesn

Store JWT token in cookie

偶尔善良 提交于 2019-12-03 07:30:47
问题 This is my setup: 1 authentication server which gives out JWT token on successfull authentication. Multiple API resource servers which gives information (when the user is authenticated). Now I want to build my ASP.NET MVC frontend. Is it ok to take the token, which I receive after authentication, and put it in a cookie so I can access it with every secured call I need to make? I use the RestSharp DLL for doing my http calls. If it has a security flaw, then where should I store my token? I

How to save Oauth Access token securely in android

青春壹個敷衍的年華 提交于 2019-12-03 07:01:30
问题 I have access token from the server after authentication lets say "uyhjjfjfgg567f8fhjkkf" now I want to save it in the device securely. I looked in Keystore and Keychain in android developer sites. I dont clearly understand how it works and how we should retrieve the token from the keystore. KeyPairGenerator kpg = KeyPairGenerator.getInstance( KeyProperties.KEY_ALGORITHM_EC, "AndroidKeyStore"); kpg.initialize(new KeyGenParameterSpec.Builder( alias, KeyProperties.PURPOSE_SIGN | KeyProperties

How to produce JWT with Google OAuth2 compatible algorithm RSA SHA-256 using System.IdentityModel.Tokens.Jwt?

霸气de小男生 提交于 2019-12-03 06:22:51
问题 I'm trying to create a JWT to authorize with a service account as described in Google documentation using System.IdentityModel.Tokens.Jwt. I have the following code: byte[] key = Convert.FromBase64String("..."); var certificate = new X509Certificate2(key, "notasecret"); DateTime now = DateTime.UtcNow; TimeSpan span = now - UnixEpoch; Claim[] claims = { new Claim("iss", "email@developer.gserviceaccount.com"), new Claim("scope", "https://www.googleapis.com/auth/plus.me"), new Claim("aud",

Is there still a way to fetch instagram feed without using access token now (06/2016)?

独自空忆成欢 提交于 2019-12-03 05:11:41
问题 I have an issue that my Instagram API access token keeps expiring frequently and I red the document and understood that although the token wouldn't expire generally, Instagram may decide to expire a token any time for any security reason or whatever reasons. I know that when it expires, I need to set up an authentication process and request for a new token and all those of things. But the problem is that my app is just retrieving my own feeds to show on my own website, once the token expires

How to store an auth token in an Angular app

£可爱£侵袭症+ 提交于 2019-12-03 05:10:23
I have an Angular application (SPA) that communicates with a REST API server and I'm interested in finding out the best method to store an access token that is returned from an API server so that the Angular client can use it to authenticate future requests to the API. For security reasons, I would like to store it as a browser session variable so that the token is not persisted after the browser is closed. I'm implementing a slightly customized version of OAuth 2.0 using the Resource Owner Password grant. The Angular application provides a form for the user to enter their username and

Where to store the personal access token from GitHub?

十年热恋 提交于 2019-12-03 04:46:41
问题 Is it necessary to store the personal access token somewhere locally on the machine after generating it in GitHub? If yes, is there any preferred way where it could be stored? 回答1: Half the point of passwords is that (ideally) you memorize them and the system hashes them, so therefore they're never stored anywhere in plain text. Yet GitHub's personal access token system seems to basically force you to store the token in plain text? First, a PAT (Personal Access Token) is not a simple password