Skip to main content
abhayd3663
May 9, 2024
Question

Authentication Types in Connected System

  • May 9, 2024
  • 13 replies
  • 0 views

We have a requirement to call web API which uses Bearer Token authentication type and it requires client id and secret in the Header.

Before calling this API we need to get the access token using oAuth endpoint, this endpoint has authentication type as Basic Auth and it requires same client id and secret in the Header.

1. For OAuth endpoint, we have created a connected system (A) with the Basic Authentication using username and password. - Works fine.

2. For the primary API, we have created another connected system (B) with the following information.

a. Base URL: <Base URL>.

b. Authentication: None

3. Created an Integration object which uses connected system B and has following parameters in the Headers.

a. Authorization: <Token received in step #1, passed as rule input>

b. X-IBM-Client-Id: <client id, passed as constant >

c. X-IBM-Client-Secret: <client secret, passed as constant>

The above setup works fine however as per our security compliance we cannot have a secret in the constant which is non-masked.

Is there a way for us to use connected system which supports the masked password and secret to achieve above scenario?

13 replies

mikes0011
Brainy
May 9, 2024
Is there a way for us to use connected system which supports the masked password and secret to achieve above scenario?

Have you looked into whether it's possible to make this work along with the Credential Store?  I don't happen to know but I'd be surprised if there isn't some way.

abhayd3663
May 10, 2024

I did not find a way to use Credential Store fields directly in the CS or Integration object.

mikes0011
Brainy
May 10, 2024

Dang, that's disappointing.  Maybe (in the meantime) open a product use case with Appian?  It seems like there should be a way to do this.  (cc [mention:6b9f80ff18f9420082d13ef2d5121d56:e9ed411860ed4f2ba0265705b8793d05] )

stefanhelzle0001
May 9, 2024

Why not add that client secret in the connected system instead of leaving authentication to "None"?

abhayd3663
May 10, 2024

We can but is there a way to refer the id and secret from CS to pass in the Header?

stefanhelzle0001
May 10, 2024

Appian will add it automatically. That's the whole point of it. But maybe I am missing something...

harshk1671
May 10, 2024

I hope you have already considered 'OAUTH 2.0: SAML BEARER ASSERTION FLOW' where client secret is masked.

https://docs.appian.com/suite/help/24.1/oauth_saml_bearer_assertion_flow.html

abhayd3663
May 10, 2024

This does not work for us. If we provide the id and secret in the Header, it will still be in plain text and will be visible.

harshk1671
May 10, 2024