Difference between revisions of "Rabora OAUTH2"
From DarkWiki
(→Customer clients) |
(→Customer clients) |
||
| Line 17: | Line 17: | ||
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. | 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 | + | ** ClientId (generated by the SSO server) |
| − | ** Secret | + | ** Secret (generated by the SSO server) |
** Application name | ** Application name | ||
| + | ** (CompanyId is fixed) | ||
| + | * Optional settings | ||
| + | ** Token refresh interval | ||
Revision as of 16:13, 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.
- Primary settings
- ClientId (generated by the SSO server)
- Secret (generated by the SSO server)
- Application name
- (CompanyId is fixed)
- Optional settings
- Token refresh interval
