Difference between revisions of "Rabora OAUTH2"
From DarkWiki
(→Rabora clients) |
(→Customer clients) |
||
| Line 15: | Line 15: | ||
===Customer clients=== | ===Customer clients=== | ||
| − | Clients running at a customer premises are associated with a '''companyId'''. | + | 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. |
| + | |||
| + | * Account details | ||
| + | ** ClientId | ||
| + | ** Secret | ||
| + | ** Application name | ||
Revision as of 16:11, 14 August 2017
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.
- Account details
- ClientId
- Secret
- Application name
