KamoCRM

Connected Apps follow-ups — Let Apps Connect Themselves, SAML signing certificate, TV or device and SAML apps, data permissions in the scope picker (Identity ID4.4b)

Featurekamo-internal
Shipped
November 15, 2026 at 3:46 PM UTC
Author
Kamo
Commit
043675e

- Settings: Let Apps Connect Themselves card (Off / Ask Me First / Approve Simple Apps Automatically → PUT settings {dcrMode}; registration address with copy; locked while the provider is off) and a SAML Signing Certificate card when settings.saml exists (expiry, download .pem, metadata address, Make A New SAML Certificate behind a confirm). - Wizard steps follow the app type: TV Or Device (no return addresses; How It Signs In step with the code picture and Can The Device Keep A Secret? → tokenAuthMethod at creation only) and SAML App (SAML Settings step: Entity ID + reply addresses or pasted metadata, Identify People By, attributes editor, Sign The Whole Response, Can Be Opened From An App Launcher + landing page). Websites/SPA/mobile get Sign In On A TV Or Device (grantTypes device_code). - Scope picker: Work With Kamo Data — the API scopes from the catalogue grouped by area, Read/Change switches, each naming the Kamo rights it needs; consent preview, app cards and People Using It show them in words. - SAML apps: details panel (metadata/entity/SSO/launch with copy, certificate), no client id or secret shown; device apps: device guide, curl + Node polling samples, .env with device endpoints. - Back-End Service stays Coming Later: SecurityService still answers APP_TYPE_NOT_AVAILABLE for MACHINE. - Help: tips + anchors; KB connected-apps, connect-an-app and the developer article updated.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing