The SharePoint-Driver provides connectivity between IOTA and Microsoft SharePoint. The SharePoint-Driver provides seamless integration between these two systems. The driver is state-less, i.e., it doesn't maintain source connections and any data caches. The single SharePoint-Driver service can support multiple connections to different Microsoft SharePoint servers.
The driver supports the following object types:
| IOTA Type | Supported? | Source Type |
|---|---|---|
| Tag | 🟢 | List - sharepoint type |
| Asset | ⚫ | |
| Timeframe | ⚫ |
Diagram
Technical Specification
| Description | Value |
|---|---|
| Development Language | GoLang |
| Processor Architecture | 64-bit |
| Supported Operating Systems | Windows/Linux/OSX |
| Deployment Size | 36.1 Mb |
| Data modes | Read |
| Request/Response pattern | Asynchronous |
| Source Communication | REST API |
| Back-end Communication | NATs message bus |
| Message bus driver type | sharepoint |
| Near Real-Time Data Updates | No |
| Multiple Sharepoint Systems | Yes |
Dependencies
The SharePoint-Driver is installed alongside the main IOTA Vue service within a containerized environment such as Kubernetes, Docker or Podman.
Security
Source Security
By default, the SharePoint-Driver service uses configured service's user identity for secure connections to Microsoft SharePoint Server.
IOTA API (back-end) Security
The SharePoint-Driver uses NATs message bus to communicate with the IOTA Vue Cluster. The two-way data traffic is encrypted using Transport Layer Security (TLS) on port 443. In addition, the message bus communication security model uses a public-key signature system based on Ed25519 called NKeys. With NKeys, the server can verify identities without ever storing or seeing private keys. The authentication system works by requiring a connecting client to provide its public key and digitally sign a challenge with its private key. The server generates a random challenge with every connection request, making it immune to playback attacks. The generated signature is validated against the provided public key, thus proving the client's identity. If the public key is known to the server, authentication succeeds.