Replies: 1 comment
|
@julojulox try 146+ , where client_credentials was incorrectly routed to the JWT bearer path and could cause client_secret_file to be treated like a private key; fixed in #45787 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi together,
I really cant get this work and I would appreciate your help. I have collector v145 with following yaml config (snip below)
extensions:
ZPages for internal debugging
zpages:
endpoint: 0.0.0.0:55679
OAuth2 authentication (client-secret flow)
oauth2client/cc_auth:
client_id_file: ./client_id_file
client_secret_file: ./client_secret_file
token_url: "/oauth/token"
However in logs I see
failed to get security token from token endpoint (endpoint "/oauth/token"); invalid key: Key must be a PEM encoded PKCS1 or PKCS8 key", "interval": "11.112083153s"}
It looks like its still pulling the cert auth instead of client secret. The client ID and secret have special characters like $ or | . Though I could not identify if this is a problem when stored in file and if yes how to overcome it. I tried everything, running out of ideas :/
When I print-config I see something stored in certificate_key but cant find out where it does come from.
extensions:
oauth2client/cc_auth:
client_certificate_key: '[REDACTED]'
client_certificate_key_file: ""
client_certificate_key_id: ""
client_id:
client_id_file: ""
client_secret: '[REDACTED]'
client_secret_file: ""
endpoint_params: {}
expiry_buffer: 5m0s
Any help is highly appreciated. Thx
All reactions