Skip to main content
Eka issues the Client ID and Client Secret for Sign in with Eka. Credentials created in the Eka Console are rejected by the sign-in flow.

Requesting an OAuth client from Eka

An OAuth client lets your users sign in with their Eka account and authorize StackOne to act on their behalf.

  • Email ekaconnect@eka.care with your organization name and intended use case, and ask for an OAuth Client ID and Secret.
  • Ask Eka to register this redirect URI for the client: https://api.stackone.com/connect/oauth2/ekacare/callback
  • Eka always grants the fixed scope set openid profile email offline_access, so there are no scopes to choose.

Adding the client to StackOne

Once Eka sends the credentials, add them to the StackOne Connector profile.

  • Paste the Client ID into the Client ID field in the StackOne Connector profile.
  • Paste the Client Secret into the Client Secret field in the StackOne Connector profile, and store it securely for use later.
  • Format: EC_ followed by digits
  • Example: EC_178843954824934

Creating the StackOne Connector Profile

To create the Connector Profile in StackOne for Eka Care:
1

Navigate to Connector Profiles

Login to StackOne and navigate to Connector Profiles
2

Create New Connector Profile

  • Click + Connector Profile
  • Search for and select Eka Care
  • Select Type as Eka Sign-In (OIDC)
  • Fill out the fields using details retrieved from your provider:
    • Client ID
    • Client Secret
  • (Optional) Select Actions to be enabled for this Connector Profile
  • Click Create profile
Congratulations! The new Connector Profile will now show up in your project ready to be used. You can now continue to Link Accounts for Eka Care.