Hi,
I am currently working on a use case that requires the generation of JWT tokens based on PKCS#8 standards. I've chosen JWT plugin for this task. However, it seems that this plugin is compatible only with private keys that are based on PKCS#1 (RSA) standards.
Is there any known workaround to fulfill this requirement ?
Thanks,
Discussion posts and replies are publicly visible
Did you try converting your pkcs 8 key into pkcs 1 and then using that with the JWT plugin?
openssl rsa -in pkcs8.key -out pkcs1.key
Yes, I tried but Snowflakes doesn't like that token, It supports PKCS#8 format only.
The JWT plugin only implements a very specific subset of alle the things that you could do to a JWT.
But, there are plugins that directly connect to Snowflake systems. Did you try these?
Yes, Most likely needs additional configuration to set it correctly.
In the certificate URL the term "snowflakecomputing.com" is double. Is that intended?
The JWT plug-in has now been updated to support PKCS#8 keys community.appian.com/.../jwt-web-token-tools
vineeta3061 I have a requirement to generate JWT token using the plug in and i am getting error "appianprivatekeypassword or appianprivatekey for Credential Store was null". Can you please let me know how you configured the key value in adminconsole to generate token?. Thanks for help
Can you provide a screenshot of the function you are calling and the corresponding Third-party credential store? It should look something like this. app.screencast.com/eKW98q8GvemuT
Thanks Shawn Bittinger , we were missing some parameter and after we inputted the key, we are able to generate the token successfully. After creation of token, we pass that to Snowflake as Key/pair JWT Auth and it says invalid JWT Token which means it doesnt accept. Can you please let us know if any solution.
I am currently using this plug-in to generate a JWT for key-pair auth in Snowflake without any issues.
1) Can you ensure that you are setting up the JWT claims per Snowflake's documentation?
2) Have you verified that the claims look as you expect when you paste the JWT into https://jwt.io/