Skip to content

e-ucm/a2

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

A2 - Authentication & Authorization

Build Status Coverage Status Dependency Status devDependency Status Code Climate Issue Stats Issue Stats

Authentication & Authorization module for Rage Analytics.

architecture-3-style-unified-and-updated pptx

Fig. 1.: Authentication & Authorization (A2) module; part of the Rage Analytics platform.

Design goals

Authentication and authorization are important concerns for multiple RAGE assets. Having a single server (this asset, A2) that can perform authentication and authorization on behalf of all other assets provides single-sign-on capabilities to those assets, and drastically reduces duplicated effort. A2 proxies all authenticated, authorized requests to the corresponding server-side assets. Server-side assets can programmatically (via API) register themselves and configure what they consider to be authorized via customizable roles.

For clients of server-side assets that are proxied behind A2, single-sign-on is completely transparent. Additionally, since A2 effectively becomes a single point of contact, client configuration is drastically simplified: only A2’s location login and credentials need to be stored, instead of each individual server-side asset’s location and login credentials.

For more details check out the A2 wiki page.