Add isSecureConnection field DataverseRequest

[michbarsinai]

note the interplay with #1368. Need to support connections that are externally secure, but forwarded in the clear, e.g. by a reverse proxy.

Part of the DataTags support.

[pdurbin]

I'm grabbing this issue to discuss with @mcrosas and @kcondon to see if it's related at all to the Support for Sensitive Data BRD. It may turn out to be a requirement we can defer until a later effort such as DataTags integration.

[pdurbin]

@michbarsinai and I discussed this issue briefly yesterday and I have a better idea of what it's about. In practice all traffic between end users and the server at https://dataverse.harvard.edu is encrypted over HTTPS but especially as we introduce other ways of getting data in and out (such as rsync in #3145) we need to make sure that these mechanisms are at least as secure at HTTPS. That's my take on it anyway. @michbarsinai said this is something we won't be working on this week or this month. Requirements will be made available to developers as part of the project to integrate DataTags with Dataverse. This issue doesn't seem to be actionable at this time so I'm going to unassign myself.

[pdurbin]

Closing in favor of #871.

[pdurbin]

I'm reopening this issue to remind us about this subtask. The most recent chatter about DataTags was at https://groups.google.com/d/msg/dataverse-community/1BtCe29Dhp0/lHoW-zNuFAAJ as @mheppler mentioned at #871 (comment)

This is a big project so #871 will need to be broken down into smaller chunks at some point.

[pdurbin]

@michbarsinai since all of this is deferred until Dataverse 5.0 can we close this issue? We'll break the project into small chunks once we get closer to starting it.

[michbarsinai]

As you wish - but can't we just tag it as "5.0" if it is going to be re-opened anyway?

…

On 27 Jun 2017, at 15:50, Philip Durbin ***@***.***> wrote: @michbarsinai <https://github.com/michbarsinai> since all of this is deferred until Dataverse 5.0 can we close this issue? We'll break the project into small chunks once we get closer to starting it. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2446 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB2UJC8iA4HbnaAE707_KyvjWL5jkc2kks5sIPqegaJpZM4FpgrD>.

[pdurbin]

Sure, tagged and closed. Thanks!