When I call the endpoint:
https://graph.facebook.com/oauth/access_token?client_id=clientID&client_secret=secretKEY&grant_type=fb_exchange_token&fb_exchange_token=VALIDACESSTOKEN
I get this answer:
access_token=NewACCESSTOKEN&expires=6271
What is the unit of the expire time? Seconds? Hours?
Thanks in advance.
It's in seconds before it expires.
i think it is in seconds. according to their docs it is around 60 days.
i got expiry time of 5152380. which comes out ~=60'
Related
I'm seeing a change that really just started yesterday afternoon, Wednesday April 6th approximately 14:00 GMT. I used to be able to trigger a Lambda function (in my case I'm using API Gateway) and I could normally see the relevant log entries show up in the AWS CloudWatch Console usually within a few seconds. As of yesterday, the logs are taking maybe up 30 minutes to show up and I'm wondering if anyone else has experienced anything similar or could point me in the right direction to check things out. Thank you in advance!
i'm going to answer (close) this question out ... a few hours ago the delay stopped. I'm now able to see logs appear in CloudWatch within a few seconds of the lambda fn. completing. Thanks all
I am implementing in-app subscriptions with Google Play and synchronize the status of those through polling to Google Play API. The subscriptions have a trial period of 3 days and I expect Google API to return paymentState=0(Pending) or 1(Received) after the trial period has expired. This does not always happen for customers that have a payment failure, as Google keeps returning paymentState=0(Free trial).
It seems Google is giving a grace period, although I don't have any grace period configured for this subscription type.
Do you know why this happens and how should I update the trial period status when the 3 days of trial have expired?
Thanks
Reported this several times to google, the issue is still present, from my experience for some orders the SUBSCRIPTION_GRACE is sent >20 hours after the current cycle ends, and if you send validation request before this notification paymentState will still have value 1 or 2 instead of 0.
We are getting the authentication token from the service which gets it from the WSO2. The expiry time that comes along with the token is not consistent. The expiry time sometimes comes less than 3600. For example: 400 or less etc. For this reason, the user is logging out if the expiry time is less. If it brings consistent expiry time i..e 3600 than the user will always log out after 1 hour which is 3600. but due to the inconsistency the user is facing problem.
Check the <TimestampSkew> value in repository/conf/identity/identity.xml.
Make it 0 if it's not already.
I am using Wso2 API Manager 1.8. I have created some apis in it, and subscribed it to an application. I Want to make the token expire time to infinte , means never expire token. I have gone through the tutorial given in wso2 site and done following changes.
refered link : Changing the default token expiration time
I have changed ApplicationAccessTokenDefaultValidityPeriod to -1 . Rest remains same. And I created new application to get the changes, Now get long integer value 9223372036854452224 ie 106751991 days) as expire time. And working fine .
Then I changed the system date to next day check whether the expire not set to zero. But my token expire time chages to 3600000 milliseconds, How this happens, even if the time reduces this much change never expecting.
I have chages the default H2 database to mysql and done same thing with this.
Then I noticed that when the day changes,the token expire time reduces from 9223372036854452224 to 3600000 milliseconds means 1hr of expire time, which is default time. Actually it have 106751991 days expire time. How this happening ?
Please help. How can I solve this problem
Set token validity time to -1 (minus one) - that means never expires (also, see if that is the value that you have in API Store on Subscriptions tab)
I have a job scheduled several days ago and the status is still Pending. Is there any way to known how much time approximately one needs to wait? Or find a queue position to estimate the progress yourself?
Request ID is 505334862.
Thanks,
Dennis.
Assuming you are talking about the Google Email Audit API, I don't think there is a way to check the progress. The only thing you can do is to retrieve status of a request to see if it is completed.
https://developers.google.com/admin-sdk/email-audit/#retrieving_status_of_a_request_for_a_user_accounts_information