userAccessTokenParser: failed to parse

[ronslow]

I got the following after logging in via Facebook

Internal Server Error

userAccessTokenParser: failed to parse "access_token=AAADPFaYO8UUBAGqmiKEoC6hNfxD22kc8ZAXZA3Occ1Nf9p1I6pJ7NxYXFwGhFJdjgA1tfVXVxbi8pbnIe42H4sUkwwE3kZD"

Any ideas?

Thanks

Robert

[meteficha]

That access token seems to be coming without an expiration time. Are you using server-side or client-side authentication?

[ronslow]

Server-side

[ronslow]

Yes, no expiration time because the App Setting allows this particular App to access the facebook account at any time. May need an upgrade to userAccessTokenParser to allow for no expiration time?

[meteficha]

So you're using the offline access permission?

The real problem is that currently the UserAccessToken constructor takes a UTCTime for expiration which would need to be changed to Maybe UTCTime. Since offline access is being deprecated I'm not too fond of refactoring a lot of code just for this use case.

A better compromise may be to just set the expiration time to the far, far future whenever it's not found. I don't like the silent nature of this fix, though.

Thoughts?

[ronslow]

That's got me thinking. My FB App needs offline access to read status updates - but I do this outside Yesod.

I am using auth-fb for a different purpose, namely to provide log in credentials which, as you say, should always be time limited. I think the answer in my case is to have another FB app, without offline access, which is used only to log in. That will solve the issue for me.

However, the purist in me says that the expiration time is definitely a Maybe!

Robert