New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Synchronize Swift server and JOSS server times #37

Closed
robert-bor opened this Issue May 26, 2013 · 1 comment

Comments

Projects
None yet
2 participants
@robert-bor
Member

robert-bor commented May 26, 2013

The server works at a certain time, whereas the server JOSS runs on probably has another time.

Make sure that when JOSS makes a call to the server that involves the calculation of time from the server (such as for temp URLs), that the Swift server time is used, not the JOSS server time.

@ghost ghost assigned robert-bor May 26, 2013

@robert-bor robert-bor closed this May 29, 2013

katta pushed a commit to twxkit/joss that referenced this issue Oct 6, 2014

katta pushed a commit to twxkit/joss that referenced this issue Oct 6, 2014

katta pushed a commit to twxkit/joss that referenced this issue Oct 6, 2014

@ffodera

This comment has been minimized.

Show comment
Hide comment
@ffodera

ffodera Oct 24, 2014

Is there any way to make this time synchronization optional like we can for caching?

The issue that I'm running into is that I want to use a non-admin user to authenticate using JOSS, in order to view information on public containers. We never get past this call due to a forbidden error on the HEAD account request.

We would want a non-admin user to be able to successful authenticate if we have public containers.

ffodera commented Oct 24, 2014

Is there any way to make this time synchronization optional like we can for caching?

The issue that I'm running into is that I want to use a non-admin user to authenticate using JOSS, in order to view information on public containers. We never get past this call due to a forbidden error on the HEAD account request.

We would want a non-admin user to be able to successful authenticate if we have public containers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment