- sara.next
- Integrations
- REST auto-implementation
Integrations · Integration models
REST auto-implementation
The most universal model for cloud applications and systems with an official API. Access changes are executed through endpoints provided by the vendor.
- level L3
- REST
- Graph API
- SCIM
Diagram
Directly to the application API
01 · sara.next
- Auto-implementation queueapproved requests
- Operation scriptscreate · change · delete · check
access token for the application
02 · Interface
- RESTofficial endpoints
- Microsoft GraphMicrosoft 365 services
- SCIMaccount management standard
03 · Target application
- Groups and rolesuser membership
- Teams and projectsassignments
- Resourcespermissions
Use cases
Typical systems for this model
Microsoft 365, SharePoint, Teams
Groups, teams and document resources.
Salesforce
Permission sets and user assignments.
ServiceNow
User roles, link to ITSM.
Google Workspace
Group-based access.
GitHub, GitLab, Azure DevOps
Repositories, projects, teams.
Oracle Fusion
Application roles — provided an administrative API is available.
Checklist
- The application has an official API for users, roles or groups
- The API lets you check the access state after a change
- A test environment is available
- The user has a stable identifier in both systems
Configuration
REST connection and scripts in brief
| Element | What it contains |
|---|---|
| REST connection | Name, system name, base URL, authentication type (None / Basic / Bearer / API Key) and credentials. |
| Implementation script | A Groovy script returns a map with the fields method, path and optional body and headers. |
| Verification script | Usually a GET request; a 2xx status means the change is confirmed. |
See sara.next on your own scenarios
During the presentation we will walk through an access request, approval, automatic execution of the change and a review — using examples from your organisation.