We are thrilled to announce that support for third-party credential store integration in Integration Service is now officially Live and Generally Available!
Customers can now securely integrate with external credential management systems such as CyberArk and HashiCorp Vault, enabling them to reference credentials stored outside of the Integration Service database — a major step forward for enterprise-grade security and governance.
Through Orchestrator Credential Store and Credential Assets, credentials stored in external vaults can now be dynamically resolved at design and runtime via Orchestrator APIs when establishing connections to systems like Salesforce, ServiceNow, Snowflake, Jira and many more.
Why this matters:
Eliminates the need to duplicate sensitive credentials across platforms
Eliminates the need reconnect/re-authenticate in case of secret key rotation
As customers begin adopting the feature, we’d love to hear your feedback, learnings, and enhancement ideas to help us continue improving the experience.
Is this supposed to work with customer built connectors? I don’t see any option to use a credentials asset for the Client Secret in a custom connector:
@postwick
This is currently not supported while configuring connection parameters within the Connector Builder experience. However, once the connector is published, fields such as password , client_secret , and api_token implicitly support this capability because they are defined as type=secret .
That said, the capability you’re requesting is already on our roadmap, including support for additional field types beyond just secret/password-based fields.
I’m confused. You said it’s not supported but then said it is supported implicitly. But it’s not. The Client Secret field does NOT have the asset option, as I showed in my screenshot.
Once you publish the connector, these fields will automatically become available to integrate with your credential asset. You won’t see them while configuring the connection’s properties and values inside the Connector Builder (like in your screenshot).
I have published this connector. We are using it. I don’t see anywhere that it lets me use a credentials asset for the Client Secret. Inside the connector is the only place to enter the Client Secret.
Yes you are correct. The solution is that “Ask the user” setting. By setting those to Yes, those values are provided when creating the connection. And then within the connection the credentials asset option is available
There are some problems with this new feature. I am trying to use it to store the Client Secret for a Connection in an Asset. So I created a “secret” Asset:
But when I try to select this Asset in the Connection, there are multiple problems:
It shows every credentials asset in the system, not for the folder I’m in
It only loads a limited number of assets and there’s no way to see the rest of them (we have a lot of assets in our system)
It shows CREDENTIAL assets not SECRET assets (so which value is it going to send back, the login ID or the password?)
There is no way to search the list for the asset you want
Basically this appears nonfunctional because it’s showing the wrong kind of assets, and the way the list is displayed we can’t actually see the asset we created so we cannot select it for the Connection parameter.
@postwick -I believe we are talking about the same problem in the email thread with Jesus Miron Lopez
Do you have availability next week? It will be good to meet you and we can talk about this issue. I’ll see if I can provide some workarounds.
This is a new issue I identified this morning. I did send an email to Jesus about it. I thought it is valuable information that people reading this post should have.
We are thrilled to announce that support for third-party credential store integration in Integration Service is now officially Live and Generally Available! 
Why this matters:
