Time in logs is 2 hours behind

New post

January 13, 2020 18:21

I'm collecting logs using the Box API and the time in the logs is two hours behind (showing pacific time). I'm in the central region and my user account is set to the central time zone. How do I fix this?

Comments

3 comments

jcleblanc

January 16, 2020 11:06
Hi ,

What type of application are you using when you are trying to fetch the logs, OAuth2 or the JWT / OAuth 2 application?

I could be wrong about assumptions here without knowing more, but here's what I'm thinking: Your enterprise admin settings for users are set so that new users are automatically set to Pacific time. If you're using a JWT application and making the call from the service account of the application (for a JWT app) and not the user account that you have set to central, it's entirely possible that the logs would be coming back as pacific time.

If that might be a case you can check by trying to fetch the current user information, then check the returned timezone to see what it may be set as. If the assumptions are correct then you can update the user for the service account to set the correct timezone if you'd like.

If all of that is wrong we can dig in further if you have details about the app type and potentially the code that you're running.

Thanks,

Jon
0

Comment actions Permalink
christinek2

January 16, 2020 11:39
Hi Jon,

Thank you for the response. I'm using OAuth2 to fetch the logs.

Is the user account I want to check the one listed under the OAuth 2.0 credentials in the application?

Thank you,

Christine
0

Comment actions Permalink
christinek2

January 16, 2020 12:38
Hi Jon,

I changed the user account I set the application up with to the correct time zone, central and verified with the get current user it is now sent to the central timezone. I am still seeing the logs with a timestamp of pacific time though.

Thank you,

Christine
0

Comment actions Permalink

Please sign in to leave a comment.