Skip to content

Add Jellyfish service provider configuration#44

Open
c1-dev-bot[bot] wants to merge 1 commit into
mainfrom
jellyfish-connector
Open

Add Jellyfish service provider configuration#44
c1-dev-bot[bot] wants to merge 1 commit into
mainfrom
jellyfish-connector

Conversation

@c1-dev-bot

@c1-dev-bot c1-dev-bot Bot commented Jun 9, 2026

Copy link
Copy Markdown

Summary

Adds a SCIM 2.0 service provider configuration for Jellyfish (engineering management / software engineering intelligence platform) to baton-scim.

  • Adds jellyfish.yaml service provider with standard SCIM 2.0 user/group field mappings, Bearer token authentication, and group membership provisioning (add/remove)
  • Updates CLI description to include jellyfish in the service provider list

Usage

baton-scim --service-provider jellyfish --api-key <JELLYFISH_API_KEY>

Open Questions (from issue research)

The following items need verification with access to a Jellyfish test account:

  1. SCIM Base URL — The apiEndpoint is set to https://app.jellyfish.co/scim/v2/ based on Jellyfish's URL patterns. The actual SCIM base URL is tenant-specific and provided in the Jellyfish admin portal. If the URL differs, users can override with --scim-config-file using a custom YAML, or this file can be updated.
  2. Role catalog — Role mapping is included with standard SCIM roles path. The issue notes the role catalog is "gated" — role sync/provisioning may need adjustment once the actual schema is confirmed.
  3. Rate limits / pagination — Standard SCIM pagination is configured. Rate limit behavior has not been confirmed.
  4. SCIM headerhasScimHeader: true (expects application/scim+json Accept header). Some SCIM providers don't require this; toggle to false if Jellyfish rejects it.
  5. Naming collision — Microsoft Entra's "Jellyfish" SCIM tutorial refers to Cogito Group's Jellyfish (securesme.com), NOT jellyfish.co. This service provider is for jellyfish.co.

Fixes: CXH-1705


Automated PR Notice

This PR was automatically created by c1-dev-bot as a potential implementation.

This code requires:

  • Human review of the implementation approach
  • Manual testing to verify correctness
  • Approval from the appropriate team before merging

Add SCIM 2.0 service provider YAML for Jellyfish, an engineering
management platform. Configures standard SCIM user/group sync with
Bearer token authentication and group membership provisioning.

Fixes: CXH-1705
@c1-dev-bot c1-dev-bot Bot requested a review from a team June 9, 2026 20:16
@linear-code

linear-code Bot commented Jun 9, 2026

Copy link
Copy Markdown

CXH-1705

@github-actions

github-actions Bot commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Connector PR Review: Add Jellyfish service provider configuration

Blocking Issues: 0 | Suggestions: 0 | Threads Resolved: 0
Review mode: full
View review run

Review Summary

This PR adds a new jellyfish.yaml SCIM service provider configuration and updates the CLI description to include jellyfish. The YAML config follows the same structure and conventions as existing providers (slack, miro, postman, zoom) with standard SCIM 2.0 user/group field mappings, Bearer token auth, and group membership provisioning. Role provisioning is intentionally omitted since the PR description notes the role catalog is gated. No issues found.

Security Issues

None found.

Correctness Issues

None found.

Suggestions

None.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No blocking issues found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants