Aldred Benedict
Aldred Benedict
Unfortunately i don't have control over the authorization server..It's a managed service which I leveraged. Are there any workarounds that can be done?
@dbclkclk exactly..the aim of the `authorization_code` flow is to get grant code to get access token..but it already expects an access token to get a grant code. Then what's the...
@maxtruxa I think the implementation for `authorization_code` flow is not correct. The authentication should be against the `User` database (probably something like Basic auth), instead of expecting an access token....
This is an important feature. @Vrtak-CZ do you have any workarounds?
@LaurentGoderre I posted the error message in my original post
@LaurentGoderre I added `ARG NPM_CONFIG_PREFIX=/home/.npm` to the `Dockerfile` but the same error occurred
@LaurentGoderre no..same path `/root/.npm` I verified that the environment variable is set during the image build ``` Step 1/42 : FROM node:10.18.1-alpine as builder ---> 547f0f86b4ad Step 2/42 : ARG...
Thanks @jtpetty works for me too
@cgchinmay issue still persists when using envoy version `v1.20.0.1-prod `
Hi @djboris9 a simpler alternative would be removing hardcoded `k8scc.yaml` from the image and relying on user-provided `ConfigMap` e.g. ``` --- apiVersion: v1 kind: ConfigMap metadata: name: org1-peer1-k8scc data: k8scc.yaml:...