authentication about opencap-processing HOT 4 CLOSED

@suhlrich another thing that Matt told me about. Currently, you need to authenticate independent of what data you want to download. So even if the session is public, you need to authenticate. Is this how we would like to proceed or do we want to check if the session is public before asking for authentication? I first thought we would want the second option, but actually having people authenticate in any case and allow them to download data from public session probably makes more sense. Let me know what you think.

from opencap-processing.

Hmm. I just checked and you can successfully make a request to a public session if you do not include the authorization header. It wouldn't be hard to implement, if session is public, set the auth token as None, and have a bunch of if statements around every request in the repo. Happy to do it if you think it is super helpful. I doubt that many people will go thru the effort of messing with a python notebook (rather than web-based plotting) if they don't have intentions of collecting data.

I'm fine with either. Your call.

from opencap-processing.

It is kinda nice to "force" people to create an account to download data? If they do not want to, then there is the dashboard for visualizing data. All this wiring for this specific case does not seem like a high level priority.

from opencap-processing.

from opencap-processing.