Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Brahmeswara Rao (Brahmesh@)
Skandiabanken
Brahmeswara Rao
Skandiabanken
SE
Brahmesh@ Member since 2013 206 posts
Skandiabanken
Posted: Apr 23, 2020
Last activity: Apr 29, 2020
Posted: 23 Apr 2020 13:38 EDT
Last activity: 29 Apr 2020 11:56 EDT
Closed

Mutual TLS isn't working with OAuth authentication profile

The internal API (connect-REST) calls are getting failed due to below error and it's happening since API gateway has been migrated from Akana to API Connect (mutual TLS). 

Error :-  Client certificates for mutual TLS in the API request doesn't match the registered certificate

It's gets resolved after keyStore is being added to Connect rule instead in OAuth provider, Is there any specific reason why it's not accepting the keystore certificates from OAuth provider.

Connect-REST :-It's working when Keystore is referred here 

Updated

Oauth profile :-  Mutual TLS isnot accepting the keystore defining in OAuth provider.

Oauth

 

 

 

To see attachments, please log in.
Pega Platform 7.3.1
Java and Activities
Security
Financial Services

Posted: 4 years ago
Posted: 29 Apr 2020 11:56 EDT
Santhosh Bagannagari (bagas)
Pegasystems Inc.
Tech Lead, Security Engineering
Pegasystems Inc.
IN

Hi,

Keystore on AuthProfile will be used in communication with Auth Provider. Keystore in Connect-REST will be used in communication with remote API server. 

Can you please share the stack trace in failure scenario ?

 

Thanks,

Santhosh

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice