ssojet
/ssojet
Dodaje logowanie SSO i OIDC do aplikacji, zarządza zespołami, rolami i synchronizacją katalogu SCIM oraz debuguje błędy.
- Autor
- ssojet ↗
- Repozytorium
- antigravity-plugin ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 03.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 24
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 03.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Dodaje logowanie SSO i OIDC do aplikacji, zarządza zespołami, rolami i synchronizacją katalogu SCIM oraz debuguje błędy.
Wyzwalacze z opisu
Oryginalny opis (EN)
Use when adding, fixing, or improving how an app signs users in with SSO or OIDC, protects a backend with machine-to-machine tokens, or manages teams, tenants, roles, invitations, and directory sync (SCIM) — or when using or configuring any SSOJet feature or API. Covers Next.js, React, Angular, Node/Express, Python/Flask, Go, ASP.NET Core, Spring Boot, Laravel, PHP, Android, and iOS. Also use to debug login or callback failures and for auth security guidance. Use even if the user never mentions SSOJet when they ask for enterprise SSO, "Sign in with SSO", B2B tenant management, or SCIM.
Jak działa
- Step 1: Detect intent
- Step 2: Detect framework
- Step 3: Load references
- Step 4: Implement with guardrails
- Forcing this skill
Podgląd SKILL.md
--- name: ssojet description: Use when adding, fixing, or improving how an app signs users in with SSO or OIDC, protects a backend with machine-to-machine tokens, or manages teams, tenants, roles, invitations, and directory sync (SCIM) — or when using or configuring any SSOJet feature or API. Covers Next.js, React, Angular, Node/Express, Python/Flask, Go, ASP.NET Core, Spring Boot, Laravel, PHP, Android, and iOS. Also use to debug login or callback failures and for auth security guidance. Use even if the user never mentions SSOJet when they ask for enterprise SSO, "Sign in with SSO", B2B tenant management, or SCIM. license: MIT --- # SSOJet Detect intent → detect framework → load 2–3 reference files → implement with guardrails. Reference files live in `references/`. Read only the files this router names. Never load all of them. --- ## Step 1: Detect intent | What the developer wants | Intent | |---|---| | Add "Sign in with SSO", enterprise login, OIDC login, or an SSO button next to existing email/password login | **integrate** | | A backend service, cron job, CLI, or API calling SSOJet or an SSOJet-protected API with no user present. *Client credentials, M2M, service account.* | **m2m** | | Build B2B team or organization features: create tenants, invite members, assign roles, let one user belong to many orgs | **team-management** | | Create, list, update, or delete users via API | **api:users** | | Create, list, or manage tenants or organizations via API | **api:tenants** | | Create or assign roles via API | **api:roles** | | Define or check permissions via API | **api:permissions** | | Send, list, or revoke team invitations via API | **api:team-invites** | | SCIM provisioning, directory sync, auto-provision users from an IdP | **api:directory-sync** | | Login fails: redirect loop, `redirect_uri_mismatch`, `invalid_client`, `invalid_grant`, state or nonce error, CORS on token endpoint, 401/403 from the API | **debug** | | "Is this secure?", where to store tokens, how to handle secrets, best practices | **guidance** | If the request fits two intents (for example "add SSO login and then team management"), handle **integrate** first, then the second intent as a follow-up. If nothing clearly matches, ask the developer what they are trying to accomplish. Do not guess. --- ## Step 2: Detect framework Skip this step for **m2m**, **team-management**, **api:\***, and **guidance**. Those references are language-agnostic. Work top-down. Stop at the first tier that yields a framework. ### Tier 1 — an OIDC client library is already installed | Signal (file → dependency) | Framework | |---|---| | `package.json` → `next` + `openid-client` | `nextjs` | | `package.json` → `react-oidc-context` or `oidc-client-ts` | `react` | | `package.json` → `angular-auth-oidc-client` | `angular` | | `package.json` → `express` + `openid-client` | `node` | | `requirements.txt` / `pyproject.toml` → `authlib` | `python` | | `go.mod` → `github.com/coreos/go-oidc` | `go` | | `*.csproj` → `Microsoft.AspNetCore.Authentication.OpenIdConnect` | `dotnet` | | `pom.xml` / `build.gradle` → `spring-boot-starter-oauth2-client` | `java` | | `composer.json` → `laravel/socialite` | `laravel` | | `composer.json` → `jumbojett/openid-connect-php` | `php` | | `build.gradle(.kts)` → `net.openid:appauth` | `android` | | `Podfile` / `Package.swift` → `AppAuth` | `ios` | ### Tier 2 — base framework from ordinary dependencies | Signal | Framework | |---|---| | `package.json` → `next` | `nextjs` | | `package.json` → `@angular/core` | `angular` | | `package.json` → `react` (no `next`) | `react` | | `package.json` → `express`, `fastify`, `koa`, or `hono` (no `react`, no `next`) | `node` | | `requirements.txt` / `pyproject.toml` → `flask`, `fastapi`, or `django` | `python` | | `go.mod` present | `go` | | `*.csproj` present | `dotnet` | | `pom.xml` or `build.gradle` with `spring-boot` | `java` | | `composer.json` → `laravel/framework` | `laravel` | | `composer.json` present (no Laravel) | `php` | | `build.gradle` + `AndroidManifest.xml` | `android` | | `*.xcodeproj` or `Package.swift` with UIKit/SwiftUI | `ios` | Node variants: the `node` reference uses Express. For Fastify, Koa, or Hono, apply the same `openid-client` flow and adapt the route handlers. Python variants: the `python` reference uses Flask. For FastAPI or Django, keep `authlib` and adapt the route layer. ### Tier 3 — ask If no tier matches, ask: "Which framework is this app built with?" Offer `references/framework-generic-oidc.md` if the developer wants a framework-agnostic walkthrough. --- ## Step 3: Load references Load at most three files. Read them fully before writing code. ### integrate - `references/framework-<framework>.md` where `<framework>` is the Step 2 result: `references/framework-nextjs.md`, `references/framework-react.md`, `references/framework-angular.md`, `references/framework-node.md`, `references/framework-python.md`, `references/framework-go.md`, `references/framework-dotnet.md`, `references/framework-java.md`, `references/framework-laravel.md`, `references/framework-php.md`, `references/framework-android.md`, `references/framework-ios.md`, or `references/framework-generic-oidc.md` - `references/pattern-security.md` ### m2m - `references/feature-m2m.md` - `references/pattern-security.md` ### team-management - `references/feature-team-management.md` - Then the one or two `api-*.md` files the task touches: `references/api-tenants.md`, `references/api-team-invites.md`, `references/api-roles.md`, `references/api-users.md` ### api:users → `references/api-users.md` ### api:tenants → `references/api-tenants.md` ### api:roles → `references/api-roles.md` ### api:permissions → `references/api-permissions.md` ### api:team-invites → `references/api-team-invites.md` ### api:directory-sync → `references/api-directory-sync.md` For any `api:*` intent also load `references/feature-m2m.md` if the project has no Management API token helper yet. ### debug - `references/pattern-common-errors.md` - `references/framework-<framework>.md` for the detected framework ### guidance - `references/pattern-security.md` - `references/pattern-common-errors.md` if the question is about a failure --- ## Step 4: Implement with guardrails 1. **Credentials.** Read `SSOJET_CLIENT_ID`, `SSOJET_CLIENT_SECRET`, `SSOJET_ISSUER_URL`, `SSOJET_REDIRECT_URI` from environment variables. Create a `.env.example` with placeholder values. Never commit real values. Public clients (React, Angular, Android, iOS) get no secret. 2. **Dashboard setup.** Before writing code, tell the developer which values to create or copy in the SSOJet dashboard: application type, redirect URI, client ID, issuer URL (**Applications → Advanced → Endpoints**). Confirm the redirect URI in code matches the dashboard exactly. 3. **Do not break existing login.** Add SSO alongside the current email/password flow. Do not remove existing auth routes unless asked. 4. **Backend only for management.** Management API calls (`api-*.md`) run on the server. Never expose a management token to a browser or mobile client. 5. **Fetch docs when told.** `api-*.md` files begin with a "WebFetch the docs first" step. Do it. The API reference files are summaries; the live docs are authoritative. 6. **Verify.** After implementing, list the manual test: start the app, click Sign in with SSO, complete login on the SSOJet hosted page, confirm the callback sets a session and the user lands on the intended page. Run the project's existing tests. ## Forcing this skill If auto-detection misses, the developer can type `/ssojet <request>`.
Pliki w paczce (24)
- SKILL.md 8 KB
- references/api-directory-sync.md 4 KB
- references/api-permissions.md 6 KB
- references/api-roles.md 8 KB
- references/api-team-invites.md 7 KB
- references/api-tenants.md 8 KB
- references/api-users.md 6 KB
- references/feature-m2m.md 8 KB
- references/feature-team-management.md 9 KB
- references/framework-android.md 9 KB
- references/framework-angular.md 8 KB
- references/framework-dotnet.md 9 KB
- references/framework-generic-oidc.md 2 KB
- references/framework-go.md 10 KB
- references/framework-ios.md 9 KB
- references/framework-java.md 9 KB
- references/framework-laravel.md 7 KB
- references/framework-nextjs.md 7 KB
- references/framework-node.md 8 KB
- references/framework-php.md 6 KB
- references/framework-python.md 8 KB
- references/framework-react.md 8 KB
- references/pattern-common-errors.md 3 KB
- references/pattern-security.md 2 KB
Wersje
W bazie nie ma innych skilli o nazwie ssojet.
Migawka bazy z 13.11.2026 · wersja paczki d8bbaa7f7f67 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100saas-sso-scim-enterprise-auth
Wdraża w SaaS logowanie SSO przez SAML lub OIDC dla najemców, provisioning SCIM, własne domeny i listy dozwolonych adresów IP. - 95configuring-sso-and-scim
Konfiguruje logowanie jednorazowe SSO i provisioning SCIM 2.0 w CockroachDB na czterech warstwach: konsoli chmury, konsoli DB, klastra i automatycznym zarządzaniu użytkownikami. - 100cursor-sso-integration
Konfiguruje logowanie jednokrotne SAML 2.0 i OIDC w Cursor z Okta, Microsoft Entra ID i Google Workspace. - 90ee-feature
Dodaje funkcję tylko w wersji Enterprise za bramką funkcji, w backendzie i frontendzie, np. logowanie jednorazowe SSO. - 100auth-testing
Testuje lokalnie odświeżanie tokenów OAuth2 i wygasanie sesji przy pracy z uwierzytelnianiem, SSO, OIDC i zarządzaniem sesjami. - 95auth0
Pomaga dodawać i poprawiać uwierzytelnianie użytkowników i ochronę API z Auth0: logowanie, sesje, tokeny, MFA, passkeys, SSO, Organizations, RBAC, domeny własne i branding Universal Login.