Skip to main content
Question

How to securely store and share tenant-specific credentials

  • February 18, 2026
  • 4 replies
  • 51 views

Forum|alt.badge.img

Hi all,

TLDR;  What is the recommended and secure way in Thinkwise to store and use tenant-specific integration credentials, comparable to how other low-code platforms handles shared variables per tenant?
 

In other low-code solutions it is was easy for me to securely store and share configuration values such as usernames, passwords or API keys per tenant. These values are centrally managed, environment-specific. They are not stored in business tables and are not accidentally overwritten during database restores.

In Thinkwise, I am currently trying to achieve something similar for integration credentials (for example, web service username and password). However, I am struggling with the best practice for:

  • Secure storage (not in application tables)

  • Environment / Tenant-specific configuration

  • Avoiding overwrite during database refreshes

  • Safe usage inside process flows and web connections

Runtime Extended Properties seem useful, but they are not easily injectable into flows without custom SQL logic. IAM configuration also does not appear to provide a straightforward way to expose secure values inside process flows.
 

Looking forward to hearing how others handle this.

Thanks!

Rolf

4 replies

  • Moderator
  • February 19, 2026

Hello @RGoossen,

Are you looking for a way to store and use integration credentials from the end applications? Or do you only need them in the IAM?

Bo Flachs


Arie V
Community Manager
Forum|alt.badge.img+12
  • Community Manager
  • February 19, 2026

@RGoossen On a general note: for integrations it is typically recommended to use the Web connector process action in combination with the Web connection configuration, which allows you to centrally (in IAM) manage the related endpoints and credentials. See the Docs for more details:https://docs.thinkwisesoftware.com/docs/sf/web_connections


Forum|alt.badge.img+2
  • Moderator
  • March 12, 2026

Hello ​@RGoossen,

Did Bo’s or Arie’s reply help you?

 


Forum|alt.badge.img
  • Author
  • Rookie
  • March 12, 2026

Hi Edo,

Thanks for checking.

The suggestions unfortunately do not fully address my use case. What I am mainly looking for is a way to store configuration values such as URLs or integration credentials securely and tenant-specific, without storing them directly in business tables.

In this case the value is used as a parameter in an x-www-form-urlencoded request, so it needs to be available inside the process flow, correct?

For now, I will look into implementing a configuration table with encrypted values to manage these settings in a controlled way.

Thanks for the input.

Rolf