Difference between revisions of "Rabora OAUTH2"
From DarkWiki
(→Introduction) |
(→Introduction) |
||
| Line 1: | Line 1: | ||
==Introduction== | ==Introduction== | ||
| − | With in {{jira}} | + | With in {{jira|id=123}} |
==Clients== | ==Clients== | ||
Revision as of 10:49, 15 August 2017
Introduction
With in 123
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
