Skip to content
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

XrdHttpExtReq should expose protocol used #619

Closed
bbockelm opened this issue Nov 12, 2017 · 4 comments
Closed

XrdHttpExtReq should expose protocol used #619

bbockelm opened this issue Nov 12, 2017 · 4 comments

Comments

@bbockelm
Copy link
Contributor

In my external handler, I want to refuse certain actions unless they were done via HTTPS.

However, there's no way to determine whether the current request came in via HTTP or HTTPS. Can we add this as a field to the request?

@xrootd-dev
Copy link

xrootd-dev commented Nov 12, 2017 via email

@bbockelm
Copy link
Contributor Author

It's not a safe assumption that any DN is present, especially as we start to transition away from client certificates...

@ffurano
Copy link
Contributor

ffurano commented Nov 13, 2017

Ok. Would it be fine for you to use SecEntity.prot and check for "http" or "https" into it ?

Please be aware that one can always use the self-redirection https->http

@bbockelm
Copy link
Contributor Author

Yes, filling in SecEntity sounds like a very good idea.

I'm doing this to avoid:

  • Using bearer tokens when working over HTTP (inherently insecure due to trivial MITM issues, particularly if we want to do this with write-based workflows).
  • Avoid inadvertent "downgrades" from HTTPS to HTTP.

@ffurano ffurano closed this as completed Apr 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants