Skip to main content
New Idea

Multiple Gainsight API Connectors for Multiple Access Keys

Related products:CS Data Management & Integrations
  • August 2, 2022
  • 9 replies
  • 164 views

benwanlessmenlo
Forum|alt.badge.img+5

I would like to be able to add multiple connectors of the type “Gainsight API”. This way each connection (integration) has its own Access Key.

Currently If I try to add more than one I received this error message:

You have reached the maximum number(1) of connections allowed for this connector.

 

Business Use-Cases:

  • When discontinuing a relationship with a vendor, I can revoke their specific Access Key without affecting any other users that are using that have API access. 
  • For security reasons, if there is a breach at a specific vendor we can quickly and securely reset or revoke their access key without interrupting other business workflows.
  • It will allow us to associate individual API calls with their source buy naming the connector separately.

9 replies

Stuart
Forum|alt.badge.img+3
  • Helper ⭐️⭐️
  • August 20, 2024

Reviving this idea from a 2-year slumber.

 

Only allowing one API key to be created at any given time is crazy (no ability to set permissions on the key, keys being visible as plain text in the edit connections box are other concerns that should be addressed).

 

Consider the following downsides:

 

  • Security Risks - if the single API key is used across multiple sources, if that key is compromised then all services relying on it are exposed to potential misuse. Additionally, it’s an increased attack surface because you can’t isolate just one key.
  • Permissions - with one key you can’t work by the security principles of ‘minimum permissions to get the job done’; would you give someone the keys to your whole house if they only needed into the shed?
  • Operational Upkeep - rotating a single key is cumbersome since the one key needs to be updated across all systems simultaneously, if it can’t then it leads to downtime.

 

tl;dr - Gainsight needs to overhaul this aspect of their application and provide the ability not just to create multiple keys, but also provide permission sets too.


matthew_lind
Forum|alt.badge.img+11
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • August 20, 2024

would you give someone the keys to your whole house if they only needed into the shed?

As a big fan of analogies for clarity, this one is next-level.


benwanlessmenlo
Forum|alt.badge.img+5
  • Author
  • Contributor ⭐️⭐️⭐️⭐️⭐️
  • August 20, 2024

I’m glad to see my 2 year old idea getting some comments!


dayn.johnson
Forum|alt.badge.img+8
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • August 21, 2024

 

...

  • For security reasons, if there is a breach at a specific vendor we can quickly and securely reset or revoke their access key without interrupting other business workflows.

Reviving this idea from a 2-year slumber.

  • Security Risks - if the single API key is used across multiple sources, if that key is compromised then all services relying on it are exposed to potential misuse. Additionally, it’s an increased attack surface because you can’t isolate just one key.
  • Permissions - with one key you can’t work by the security principles of ‘minimum permissions to get the job done’; would you give someone the keys to your whole house if they only needed into the shed?
  • Operational Upkeep - rotating a single key is cumbersome since the one key needs to be updated across all systems simultaneously, if it can’t then it leads to downtime.

 

tl;dr - Gainsight needs to overhaul this aspect of their application and provide the ability not just to create multiple keys, but also provide permission sets too.

 

So, so many concerns here -- the security ones are especially concerning for me! @kstim for awareness.


alizee
Forum|alt.badge.img+13
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • November 19, 2024

would you give someone the keys to your whole house if they only needed into the shed?

As a big fan of analogies for clarity, this one is next-level.

Love this. In building management / construction, we call this a master key system. 

 


  • Contributor ⭐️
  • January 5, 2026

+1 to this idea. With the recent security incident and following Gainsights recommendations to rotate keys, we’ve been actively reviewing and updating credentials across our connections. Relying on a single shared, full-access API key for multiple integrations is concerning. We would love to have support for multiple API keys with scoped permissions or at least multiple keys so we can rotate them easier as needed.


bradley
Forum|alt.badge.img+9
  • Expert ⭐️
  • January 5, 2026

@benwanlessmenlo with a nearly prophetic request from three years ago! 100% agree, that especially in light of...recent events, this is no longer just a “nice to have”. ​@revathimenon can we make sure someone in the security realm at Gainsight has 👀on this?


jordan_cook
Forum|alt.badge.img+3
  • Contributor ⭐️⭐️⭐️⭐️⭐️
  • January 5, 2026

Going to help dogpile on this request. With the recent security incident, and the latest recommendation to rotate API keys, I think this is going to be a must-have for anyone that really uses the Gainsight API. Almost every other solution with API access out there allows you to generate multiple keys for different integrations. Can Gainsight work like this? Allow us to generate a key for a specific purpose. Never allow us to see that key again. But allow us to revoke keys as needed.


  • Contributor ⭐️⭐️
  • January 9, 2026

We integrate data from different sources, each supported by a different team. It would be helpful to be able to rotate the key for each integration separately in co-ordination with one team, rather than coordinating with all teams at once.