Difference between revisions of "Rabora Security"
From DarkWiki
(→Introduction) |
(→Introduction) |
||
| Line 3: | Line 3: | ||
All systems and users that communicate with Rabora systems use authentication and authorisation services provided by the Rabora Security platform. In general, security is maintained through [https://en.wikipedia.org/wiki/HTTPS HTTPS] and [https://en.wikipedia.org/wiki/OAuth#OAuth_2.0 OAUTH2], with varying degrees of cryptography. | All systems and users that communicate with Rabora systems use authentication and authorisation services provided by the Rabora Security platform. In general, security is maintained through [https://en.wikipedia.org/wiki/HTTPS HTTPS] and [https://en.wikipedia.org/wiki/OAuth#OAuth_2.0 OAUTH2], with varying degrees of cryptography. | ||
| − | The Rabora Security platform provides the following | + | The Rabora Security platform provides a user interface to deal with the following: |
* Authenticate users (using a username and password) | * Authenticate users (using a username and password) | ||
| Line 9: | Line 9: | ||
** Grant/deny access to 3rd parties | ** Grant/deny access to 3rd parties | ||
** Assign ClientId/Secret for their internal machines for automation | ** Assign ClientId/Secret for their internal machines for automation | ||
| + | ** Manage relationships between companies | ||
Revision as of 13:26, 15 August 2017
Introduction
All systems and users that communicate with Rabora systems use authentication and authorisation services provided by the Rabora Security platform. In general, security is maintained through HTTPS and OAUTH2, with varying degrees of cryptography.
The Rabora Security platform provides a user interface to deal with the following:
- Authenticate users (using a username and password)
- Allow users to control access to their data
- Grant/deny access to 3rd parties
- Assign ClientId/Secret for their internal machines for automation
- Manage relationships between companies
