Feature request: Disable authentication for specific locations

[Justkant]

Is this a request for help? : no

What keywords did you search in NGINX Ingress controller issues before filing this one? : cert-manager auth authentification basic

---

Is this a BUG REPORT or FEATURE REQUEST? (choose one): FEATURE REQUEST

NGINX Ingress controller version: v0.11.0

Kubernetes version (use kubectl version): v1.8.6

What happened:
cert-manager fails to get certificates on ingress protected with authentication (e.g. basic auth)

What you expected to happen:
cert-manager should be able to provision certificates for any ingress

How to reproduce it (as minimally and precisely as possible):
You need cert-manager deployed with the ingress-shim and an ingress with those annotations:

# type of authentication
nginx.ingress.kubernetes.io/auth-type: basic
# name of the secret that contains the user/password definitions
nginx.ingress.kubernetes.io/auth-secret: basic-auth

Anything else we need to know:
nginx-ingress could bypass the auth check (if nginx conf allows it) for a given list of locations. (and probably default to /.well-known/acme-challenge)
In the same way that #2203 fixes problems with tls upgrades.

[Justkant]

Linked to cert-manager/cert-manager#235

[Justkant]

I close this because there is already a way to manually modify any Certificate Resource that the ingress-shim creates to avoid using the same ingress. (see cert-manager/cert-manager#235 (comment) or acme-http-validation)
The only thing missing is an annotation that the ingress-shim could use to automatically switch between using the same ingress and creating a new one.
Closing in favor of cert-manager/cert-manager#235