You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is possible to setup a context with a api url that contains authentication credentials for basic auth but when the cli does request to the api they get omitted.
Traefik is a cloud native reverse proxy / load-balancer. In this setup traefik searches docker for running containers and routes traffic based on labels it finds on the containers.
Check that the fn api is up and requires basic authentication.
$ fn create context --api-url "http://fn:[email protected]" auth
Successfully created context: auth
$ fn use ctx auth
Now using context: auth
$ fn list contexts
CURRENT NAME PROVIDER API URL REGISTRY
* auth default http://fn:[email protected]
default default http://localhost:8080
Query something
$ fn list apps
Fn: &{ } (*modelsv2.Error) is not supported by the TextConsumer, can be resolved by supporting TextUnmarshaler interface
See 'fn <command> --help' for more information. Client version: 0.5.81
Unfortunately this error message is not really user friendly / understandable. But it is possible to use the traefik Total Status Code Count at http://localhost:8080/dashboard/status to see that the proxy responded with 401 Unauthorized.
I also used a http debug proxy (charles) to verify that the a authorization header is missing on the requests to the backend.
Expected behaviour
A better error message in cases where api calls do not succeed.
If it is possible to setup an api url with basic auth credentials i expect them to be used for request. Or at least not be able the successfully configure a api url with credentials
The text was updated successfully, but these errors were encountered:
It is possible to setup a context with a api url that contains authentication credentials for basic auth but when the cli does request to the api they get omitted.
Steps to reproduce:
Traefik is a cloud native reverse proxy / load-balancer. In this setup traefik searches docker for running containers and routes traffic based on labels it finds on the containers.
Unfortunately this error message is not really user friendly / understandable. But it is possible to use the traefik
Total Status Code Count
at http://localhost:8080/dashboard/status to see that the proxy responded with401 Unauthorized
.I also used a http debug proxy (charles) to verify that the a
authorization
header is missing on the requests to the backend.Expected behaviour
The text was updated successfully, but these errors were encountered: