Creating an HTTP destination with OAuth2SAMLBearerAssertion authentication

Question

Hi All,
I'm trying to create an HTTP destination with OAuth2SAMLBearerAssertion authentication.
However, I'm at a loss as where to put the secret/private key. It should be part of the call to the token service so must be populated somewhere. But where? I'm guessing if I create a destination via a file, there is some parameter that I could set that should contain this key, but I'm not sure what it is - certainly there is nowhere on the HCP cockpit screen that I can use.
Downloading an existing destination that works, it looks like there is an additional "Password" parameter, but when I populate that with the private key, my connection still doesn't work.
Is there a special format that this private key must be entered into the destination file?
Many thanks for you help!
Cheers,
Chris

Answer 1

Hi Timo,
unfortunately not.
There is also a need to pass the private key to the token generation - or to somehow get the public key that is used by HCP so that I can populate that into my remote system..
eg for getting a SAML assert from SuccessFactors I can use (values abbreviated and altered)
https://apisalesdemo8.successfactors.com/oauth/idp?client_id=NWI2YTMyOTdiNjA0ZmYy...kZjM2NTU2NQ&user_id=admin&token_url=…
This generates a SAML assertion (nice of them) that I can use to get a token.
https://apisalesdemo8.successfactors.com/oauth/token?company_id=HCPDISCC&assertion=PD94bWwgdmVy..==&client_id=NWI2YTMyOT…
The receiving system (SuccessFactors) checks the SAML assert against the public key I have maintained against the client key on their side and grants the OAuth token which is used for subsequent authorisation.
So somewhere I need to either - populate the system I am calling with a public key for the private key that is being used to sign the SAML assertion, or somehow pass the private key for the public key that is being used on the called system.
I can't figure out how to do that, I'm guessing that perhaps it is more that there is a public key that I should be using on the receiving end, but not sure where I could find that.
here's a screenshot of a working SuccessFactors connection...
and no TrustStoreLocation so - I don't think it's using a truststore for the certificate...
according to the doco - When the OAuth authorization server is called, it accepts the trust settings of the destination.
Perhaps it is using the public key of the Local Service Provider in "Trust"? Certainly if this is the case it's not very obvious! (but I'm going to try!)
Cheers,
Chris