@Nagendra Babu Hi,

I understand you’re trying to pass the client ID and secret dynamically, likely for different environments or applications. However, storing the client secret unmasked in a database table is not recommended and is considered a security violation in most organizations. Pega stores the secrets in the Authentication Profile rule as per industry standard encryption and masking.

To achieve a dynamic authentication profile:

1. Create multiple Authentication Profile rules for each client ID and secret, and add these to a new Application Setting rule. This Application Setting rule can then be referenced in connectors, allowing the system to pick the correct values based on the environment.
2. For more control over authentication profiles within a single environment, you can pass dynamic values to the Application Setting using a DataPage with the syntax =DATAPAGE.PROPERTY. Here, you would only store the Authentication Profile rule name in the database table and pass it dynamically to the connector via Application Settings.

Let me know if you need more information on this approach.