This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

facebook expires period

Oct 2nd, 2012, 04:17 AM

Hi All,

I've been through many articles and everyone says Facebook token is valid for 60 days. I've tried many times with my app and the token I get is only valid for 10 days. When I searched google regarding this problem, I found the following article, which says it is a bug in spring social. Is this bug being worked on? How do I get to know the status of it?

How do you track the status of these things? Well, the best thing to do is to report the issue in JIRA (as mentioned above) and then when I (or anyone else) does any work on it, you'll be notified. Since it's a bug, it will definitely be worked on soon.

Know, however, that unless there's a huge demand for it, I'm not likely to cut a Spring Social 1.0.3 release for this bug fix. It's a bug, no doubt, but the fact that the token will actually be good for 60 days, it is not a high priority bug. (That is, if you assume the 10 days to be correct and renew every 10 days, it will still work.) Instead, I will move forward with it to be fixed in 1.1.0.BUILD-SNAPSHOT first and then 1.1.0.M1 when I cut that release (planned for the next couple of weeks).

Also note that as part of 1.1.0.M1, I plan to include a new feature to *automatically* handle invalid tokens regardless of why they are invalid (expired, revoked, etc). I'm about 80% complete with that work and hope to tie up loose ends in time for the 1.1.0.M1 release.

How do you track the status of these things? Well, the best thing to do is to report the issue in JIRA (as mentioned above) and then when I (or anyone else) does any work on it, you'll be notified. Since it's a bug, it will definitely be worked on soon.

Know, however, that unless there's a huge demand for it, I'm not likely to cut a Spring Social 1.0.3 release for this bug fix. It's a bug, no doubt, but the fact that the token will actually be good for 60 days, it is not a high priority bug. (That is, if you assume the 10 days to be correct and renew every 10 days, it will still work.) Instead, I will move forward with it to be fixed in 1.1.0.BUILD-SNAPSHOT first and then 1.1.0.M1 when I cut that release (planned for the next couple of weeks).

Also note that as part of 1.1.0.M1, I plan to include a new feature to *automatically* handle invalid tokens regardless of why they are invalid (expired, revoked, etc). I'm about 80% complete with that work and hope to tie up loose ends in time for the 1.1.0.M1 release.