Difference between revisions of "Rabora Security"
From DarkWiki
(→Endpoints) |
(→Endpoints) |
||
| Line 19: | Line 19: | ||
|- | |- | ||
|https://auth.rabora.com/oauth/authorize||Central OAUTH2 authorisation endpoint | |https://auth.rabora.com/oauth/authorize||Central OAUTH2 authorisation endpoint | ||
| + | |- | ||
| + | |https://auth.rabora.com/oauth/token||Central OAUTH2 token endpoint | ||
|- | |- | ||
|https://security.rabora.com/||Security Management UI | |https://security.rabora.com/||Security Management UI | ||
Revision as of 10:35, 8 September 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
Endpoints
| URL | Notes |
|---|---|
| https://auth.rabora.com/login | Central login |
| https://auth.rabora.com/oauth/authorize | Central OAUTH2 authorisation endpoint |
| https://auth.rabora.com/oauth/token | Central OAUTH2 token endpoint |
| https://security.rabora.com/ | Security Management UI |
| https://security.rabora.com/api/ | Security Management API |
| https://security.rabora.com/api/swagger-ui.html | Security Management API documentation |
