[portal] Skip auth when admin endpoints are exposed on an internal port.

Will be used in k8s environment, at least initially. This approach assumes we
don't expose any really critical information/abilities via /admin/portal pages.

If we ever do, we should figure out a better authentication story (perhaps piggy
back on k8s auth somehow). Few hours of research didn't find anything easily
implementable.

R=jchinlee@chromium.org, nodir@chromium.org, tandrii@chromium.org
BUG=959427

Change-Id: I99d5cd73786e86bd093ccf5d74d8d7c56e1c3e07
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/1621749
Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
Reviewed-by: Nodir Turakulov <nodir@chromium.org>
Reviewed-by: Jao-ke Chin-Lee <jchinlee@chromium.org>
1 file changed
tree: 372198989e0617413d5c3f5eb0d319e31bbb03e5
  1. appengine/
  2. auth/
  3. buildbucket/
  4. cipd/
  5. client/
  6. common/
  7. config/
  8. cq/
  9. dm/
  10. examples/
  11. gce/
  12. grpc/
  13. hardcoded/
  14. logdog/
  15. luci_notify/
  16. lucicfg/
  17. lucictx/
  18. machine-db/
  19. milo/
  20. mmutex/
  21. mp/
  22. scheduler/
  23. scripts/
  24. server/
  25. starlark/
  26. swarming/
  27. tokenserver/
  28. tools/
  29. tumble/
  30. vpython/
  31. web/
  32. .gitattributes
  33. .travis.yml
  34. AUTHORS
  35. codereview.settings
  36. CONTRIBUTING.md
  37. CONTRIBUTORS
  38. LICENSE
  39. OWNERS
  40. pre-commit-go.yml
  41. PRESUBMIT.py
  42. README.md
README.md

luci-go: LUCI services and tools in Go

GoDoc

Installing

LUCI Go code is meant to be worked on from an Chromium infra.git checkout, which enforces packages versions and Go toolchain version. First get fetch via depot_tools.git then run:

fetch infra
cd infra/go
eval `./env.py`
cd src/go.chromium.org/luci

Contributing

Contributing uses the same flow as Chromium contributions.