Difference between revisions of "Onepoint"
(→Secondary Backends) |
(→Directory Backends) |
||
Line 30: | Line 30: | ||
=== Directory Backends === | === Directory Backends === | ||
+ | |||
+ | Responsible for managing directory data (user, groups and membership). It's a extensible backend type, allowing integration of external directories. | ||
+ | |||
=== Ticketing Backends === | === Ticketing Backends === | ||
=== Vault Backends === | === Vault Backends === |
Revision as of 14:57, 17 October 2018
Contents
Introduction
Onepoint enables Systems Integration for the IT environment. Through its disciplines concepts, it allows the integration of IT assets, modules, systems and units into a single and widelly connected among all parts, creating the possibility to creating actions, tasks and flows involving all those parts.
Architecture
Onepoint components:
Backends
Backends are a Onepoint-specific concept. They are components of the computational environment designed to carry out a task or a group of related tasks for a Discipline. They allow requests and operations on the target systems through Onepoint REST calls. They also allow the integration of asynchronous tasks directly on the target systems, through Onepoint Scripts calls.
Primary Backends
Primary Backends are backends that can be instanced, parameterized and extended to integrate environment's own components, such as vaults, user directories, ticketing systems, authentication systems and authorizations systems.
Authentication Backends
Responsible for user identity authentication. After a positive response from 'login' operation, Onepoint generates a session for operating the system. It's an extensible backend. In other words, it's possible to integrate other authenticators into onepoint, including supporting Multi-Factor Authentication and Single Sign-On tools.
Directory Backends
Responsible for managing directory data (user, groups and membership). It's a extensible backend type, allowing integration of external directories.
Ticketing Backends
Vault Backends
Access Session Backend
Secondary Backends
Secondary Backends are internal and/or fixed backends, that can't be instanced, parameterized or extended.
Authorization Backends
Responsible for verification of permissions on the requested resource(s) for the logged in identity. It's not an extensible backend. It works with permissioning based on Access Control Lists, Groups and Inheritance support