• Join - It's Free

How to extend the time until the authorization ends

Started by Kenneth Ekman on Thursday, December 6, 2018
Problem with this page?

Participants:

Related Projects:

Showing all 8 posts

Hi,

I am trying out my new site at http://improveyourtree.com which is working decently, although still in development.

One thing I'm having problems with is that the time until the geni authentication runs out runs out after a while, sometimes in the middle of a tree analysis. For example yesterday evening, when I started a job, it was aborted after thirty minutes, although the job should have taken a few hours. What happened (I think) is that the time "left" on my authentication session was just 30 minutes, since I had started a job the night before which had some time left, so although I did re-authenticate myself I did not get 24 more hours, it just continued counting on the session started 23 hours before. That meant that after half an hour geni returned 401 Not Authorized on all my reguests. (Restarting the same job this morning worked nicely)

Do you have any good hint about how to handle this? How can I request 24 "new" hours every time I start a job?

(I'll admit that I do not fully understand how I am supposed to use the different types of authentication that geni provides...)

You are welcome to try the site. It's free to register, and analyze your geni or gedcom trees!

Hi Kenneth,

At any time you can use the refresh token to reset the clock. See the documentation at the bottom of https://www.geni.com/platform/developer/help/oauth_server_side?vers...

cheers,

Mike

Ok,

At the initial web-authorization I just get an access_token, and an expires_in, no refresh_token. Maybe I'm using the wrong type?

I will look into this further this weekend.

My app is registered as type Web as opposed to "Native/Desktop". I assume that is correct?

What value did you specify for the 'response_type' parameter in the first authorization step? It should either be omitted or given with value 'code'. I think you are using the client side flow which does not allow for refreshing the authentication token.

The Client Side Flow in Geni documentation is apparently using the OAuth 2.0 Implicit Grant type and Server Side Flow the OAuth 2.0 Authorization Code Grant type. Former is no longer recommended to be used by the "OAuth 2.0 Security Best Current Practice", see https://oauth.net/2/grant-types/implicit/.

Ahh, Im using response_type = token...

Works nicely after I changed that!

Showing all 8 posts

Create a free account or login to participate in this discussion