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
Any attempt to use JWT Oauth2 results in the error
Steps to reproduce
Generate a private key eg.
openssl genrsa -out private-key.pem
Copy contents or private-key.pem into Private key field in infinity plugin
Hit Save & Test
Receive error:
private key should be a PEM or plain PKCS1 or PKCS8; parse error: asn1: structure error: tags don't match (16 vs {class:0 tag:13 length:45 isCompound:true}) {optional:false explicit:false application:false private:false defaultValue:<nil> tag:<nil> stringType:0 timeType:0 set:false omitEmpty:false} pkcs1PrivateKey @2
Screenshots
In this scenario i was trying to set up connectivity to a salesforce Sandbox environment (Environment will be trashed shortly so not concerned with sharing details)
Whilst the screenshot mentioned the health check url being polled its not actually getting that far as the error is occurring in generating the payload to send to the token URL and generate the JWT. Ive been able to connect to the same instance using client credentials but this is insufficient for the use case.
You can generate the same error with just the Private key, the allowed hosts and the health check fields configured. Everything else can be blank and the same private key error will appear
Version Details:
Grafana version : v11.2.0-74515 (cloud)
Plugin version : 2.9.5 (Updated whilst troubleshooting
The text was updated successfully, but these errors were encountered:
Describe the bug
Any attempt to use JWT Oauth2 results in the error
Steps to reproduce
Generate a private key eg.
openssl genrsa -out private-key.pem
Copy contents or private-key.pem into Private key field in infinity plugin
Hit Save & Test
Receive error:
Screenshots
In this scenario i was trying to set up connectivity to a salesforce Sandbox environment (Environment will be trashed shortly so not concerned with sharing details)
Whilst the screenshot mentioned the health check url being polled its not actually getting that far as the error is occurring in generating the payload to send to the token URL and generate the JWT. Ive been able to connect to the same instance using client credentials but this is insufficient for the use case.
You can generate the same error with just the Private key, the allowed hosts and the health check fields configured. Everything else can be blank and the same private key error will appear
Version Details:
The text was updated successfully, but these errors were encountered: