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 the Callback URL from your Connector Profile as the redirect URI for the client.
  • 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 StackOne Hub.
  • 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

Open the connector

Log in to StackOne, open Connectors, and select Eka Care.
2

Choose actions and events

  • Click Add Profile.
  • If the connector offers more than one authentication method, set the Auth Method filter to Eka Sign-In (OIDC).
  • Select the actions, and any events, to enable for this Connector Profile.
  • Click Continue.
3

Set up authentication

  • Select Authentication Type as Eka Sign-In (OIDC).
  • Fill out the fields using details retrieved from your provider:
    • Client ID
    • Client Secret
  • Click Create Profile.
Congratulations! The new Connector Profile now shows up on the connector page. If you created it as a project member rather than an admin, it starts disabled until a project admin enables it. You can now continue to Link Accounts for Eka Care.