Difference between revisions of "Rabora OAUTH2"
From DarkWiki
(→Introduction) |
(→Clients) |
||
| Line 28: | Line 28: | ||
* Optional settings | * Optional settings | ||
** Token refresh interval | ** Token refresh interval | ||
| + | |||
| + | ===3rd-party clients=== | ||
| + | |||
| + | Customers can allow 3rd parties access to their data. In this instance, the '''companyId''' is locked to that of the user account that granted the access. | ||
| + | |||
| + | * Primary settings | ||
| + | ** ClientId (generated by the SSO server) | ||
| + | ** Secret (generated by the SSO server) | ||
| + | ** Application name | ||
| + | ** (CompanyId is fixed) | ||
Revision as of 12:58, 15 August 2017
Introduction
With in RABSEC-10
Clients
Rabora clients
Rabora clients are automatically approved by the OAUTH2 Authentication & Authorisation server, giving the Single Sign-On (SSO) capability across the whole Rabora domain. The following scopes are relevant to Rabora clients:
| Scope | Purpose |
|---|---|
| rabora:external | The client is accessible via a public interface (such as a UI application or public API). |
| rabora:internal | The client runs within the Rabora infrastructure. |
Customer clients
Clients running at a customer premises are associated with a companyId. There is a virtual user associated with the client_details account, and is named the same as the customer's application.
- Primary settings
- ClientId (generated by the SSO server)
- Secret (generated by the SSO server)
- Application name
- (CompanyId is fixed)
- Optional settings
- Token refresh interval
3rd-party clients
Customers can allow 3rd parties access to their data. In this instance, the companyId is locked to that of the user account that granted the access.
- Primary settings
- ClientId (generated by the SSO server)
- Secret (generated by the SSO server)
- Application name
- (CompanyId is fixed)
