Multiple Authentication Methods for a Single Custom App: Best Practices?

Features
1

Hello Make.com community!

We are the developers of Kintone.com, a business application platform, and we’re creating a custom app for Make.com integration.

Our situation:

We offer three different authentication methods for our API:

  • Password authentication
  • API token authentication
  • OAuth 2.0 authentication

The challenge:

When developing Action modules (like “Get Record”), we’ve noticed that the module configuration UI only allows setting up one primary Connection and one Alternative Connection (advanced). However, we want to offer all three authentication methods to our users.

Our questions:

  1. Is it possible to associate more than two Connection types with a single module, allowing users to choose from all three authentication methods?
  2. If not, what are the best practices for offering multiple authentication methods in a custom app?
  3. Should we create separate modules for each authentication method (which seems redundant), or is there a more elegant approach?

We’d appreciate any insights, examples, or recommendations from developers who have faced similar challenges when implementing multiple authentication options in their custom apps.

Thank you in advance for your help!

2

Hi and welcome to the Community!

As Kintone has signed up to our Technology Partner Program, I’d suggest raising your request through the Tech Partner Program channels. I’ve DM’d you the name and email of the primary contact we have for you.

1 Like