I have a .pem and .key file provided by ADP. I have uploaded to the Admin Console under "Certificates" --> "Trusted Server Certificates", when I add it to the "Client Certificates" I get a error for missing key file even though I'm not sure how to add it as well since its only looking for a .pem file.
First question: is this correct to add it under the "Trusted Server Certificates" to use in an integration that calls the web service or should it be in "Client Certificates" and if so, how do I add the key?
Now I read in the documentation that you're supposed to create a "Connected System" with HTTPS and set Authentication to "None". But I have a client id and client secret to add but to the body.
Second question: Do I create a Connected System with None Authorization, then create an Integration that adds the client id/client secret to the Body in there?
Third question: how do I utilize the client certificate in the Integration, is there a function that calls it? Or do I add it somehow in the Connected System?
Fourth question: The token needed to be used for the API call, how do I add that in the integration throughout its lifetime?
Thank you all.
Discussion posts and replies are publicly visible
Do you have any experience using SSL certificates?
1) Depends on whether you use the certificate to authenticate the client to the server. If this is the case then it must go to "Client Certificates". The message body is created in the integration.
2) Yes
3) This is done automatically by matching the url in the certificate to the server you call.
4) Which token? You would add it in the integration as a query parameter, a header or in the body.
I do not, this is the first one I've used. With Appian is not as straightforward as there is no documentation for this case use. I've set it up with Postman but there are examples for its usage so it was much easier.
#1: I believe the certificate is used to authenticate the client to the server. I'm assuming ADP would use this methodology. Why do I get the missing key error? Am I suppose to use openSSL to create a combo file such as a .csr or a .pfx (which I have already but when I upload it does not take it and wants specifically a .pem file)? I do have a .key file as well, but I don't see an option to add it along with the .pem file.
#2: Understood.
#3: I figured it would be an Appian function that would be called in the initial setup when it was called, but makes sense.
#4: The token that the Token Request Endpoint returns in order to use for every API call, but I see what you mean now.
Thank you for the quick response
https://docs.appian.com/suite/help/21.2/connected_system_authentication.html
https://docs.appian.com/suite/help/21.2/Appian_Administration_Console.html#client-certificates
I think the client cert needs to be a combined file.