Skip to main content
Completed

Enable/Disable PKCE for OAuth User Login Connector

Related products:Software FactoryIntelligent Application ManagerIndicium Service Tier

Currently, the OAuth User Login connector within Thinkwise always requires the use of PKCE (Proof Key for Code Exchange). While PKCE is a secure method for protecting the authorization code exchange, there are still OAuth servers and systems that do not support this method. This can pose challenges for integrations where PKCE support is unavailable.

 

To facilitate integration with such systems, it would be beneficial if Thinkwise provided the option to enable or disable PKCE based on the server configuration. This would increase flexibility and help simplify integrations with various OAuth servers.

Did this topic help you find an answer to your question?

4 replies

Forum|alt.badge.img+4

Hello @Roald Heiwegen,

We will be implementing this in version 2024.3 of the platform, which will be released in early October.


Mark Jongeling
Administrator
Forum|alt.badge.img+23
NewWorking on it!

Forum|alt.badge.img+1

@Vincent Doppenberg  Thanks!! I'm currently facing a blocking issue with authentication and refresh tokens.


Jeroen van den Belt
Administrator
Forum|alt.badge.img+9
Working on it!Completed

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings