Generate JWT Token By External System Key

Check this documentation: https://docs.appian.com/suite/help/23.4/Secure_Credentials_Store.html

Hi Stefan,

Thanks for your quick response.

there is no proper tutorial mentioned there, like what are the things are required to do on external system and there is button on Test connection to test the details with the external system.

getiing error like this - 

"appianprivatekeypassword or appianprivatekey for Credential Store was null"(Text)

thanks,

Shree krishna tiwari

Do you have a problem related with this?

createtokenwithcustomclaims(
  externalSystemKey:"JWTKey", 
  sub:"bdn-3jOZsAi38MUo5PWhwyHP57tLWZnHspHPztA1HtKD", 
  iss:"bdn-3jOZsAi38MUo5PWhwyHP57tLWZnHspHPztA1HtKD", 
  alg:"PS256", 
  typ:"JWT",
  aud:"XXX", 
  jti:"jti111111111111673416931964", 
  exp:1709635533, 
  kid:"8879137017532837800857709831293634212", 
  x5t:null, 
  ver:null, 
  claims:null
)

Yes. I've configured the third party credentials with private key and used it in expression. However I received the same output "appianprivatekeypassword or appianprivatekey for Credential Store was null"

Hi Vijay

Check The Screen shots attached and follow the below steps -

1. Generate Public Key and Private Key , its okay to generate it from online tool too for testing, but later need to change it

2. Go to third party credentials in admin console

3. Create one credentials, its name is your external system key 

4. register field names as you are geeting error for the same key name and add public key generated as value as shown in screenshots for 2 and 3 point

5. allow your plugin to use 3rd party credentials 

thats all you need to do, if its configured correctly as steted above, you will be able to generate jwt token

Hi shreekrishnat0001 , Thanks for quick response. I've set up the below things, yet receiving same response.

How to test the connection in third party Credentials.?

createtokenwithcustomclaims(
  externalSystemKey:"JWTTokenKey", 
  sub:"bdn-3jOZsAi38MUo5PWhwyHP57tLWZnHspHPztA1HtKD", 
  iss:"bdn-3jOZsAi38MUo5PWhwyHP57tLWZnHspHPztA1HtKD", 
  alg:"PS256", 
  typ:"JWT",
  aud:"https://token.tiaa.XXX.com/as/token.oauth2", 
  jti:"jti111111111111673416931964", 
  exp:1709635533, 
  kid:"8879137017532837800857709831293634212", 
  x5t:null, 
  ver:null, 
  claims:null
)

Hi Vijay,

I think you may have missed configuring third party credentials in admin console

- prepare public key and private key 

- Goto admin console, 

- configure third party credentials 

- create two field appianPrivateKey and public key,

- Note: public and private key name should be exactly the same as you are getting error

- after this you need to pass same external system key in token functions

Hope this should work,

Thanks

Hi, 

Seems your configuration is correct, I seen it.

try it out and check if format of public key and private key is correct 

The key format is correct. I'm able to generate the token manually in jwt.io

Could you pleas tell me what is the Test Connection section. Please share me any sample expression.

Hi shreekrishnat0001 ,
I also have one use case related to JWT but i am not able to setup Third Party Credentials as i am getting confused in generation of appianprivatekey and appianprivatekeypassword. Can you please help me in this?

To test the connection:

docs.appian.com/.../Appian_Administration_Console.html

you were right. shreekrishnat0001  The key format must be in RSA.

We found that the Private Key was in the following format: "-----BEGIN ENCRYPTED PRIVATE KEY-----"
However, the tool was expecting RSA: "-----BEGIN RSA PRIVATE KEY-----"

We used the following command to convert to the proper format:
openssl rsa -in privatekey.pem -out privatekey_out.pem

you were right. shreekrishnat0001  The key format must be in RSA.

We found that the Private Key was in the following format: "-----BEGIN ENCRYPTED PRIVATE KEY-----"
However, the tool was expecting RSA: "-----BEGIN RSA PRIVATE KEY-----"

We used the following command to convert to the proper format:
openssl rsa -in privatekey.pem -out privatekey_out.pem