16. Annex 8: TACACS Based Authentication Support In OSM
16.1. Introduction
Terminal Access Controller Access-Control System (TACACS) refers to a family of related protocols handling remote authentication and related services for networked access control through a centralized server.
OSM NB has a plugin which can interact with TACACS server to authenticate users.
16.2. Integration
16.2.1. Prerequisite for Integration
TACACS host ip address reachable from OSM.
TACACS server secret(or password).
16.2.2. Integration Steps
Configure NBI to use TACACS plugin, by modiifying nbi.cfg
:
Set
authentication.backend
astacacs
Set
authentication.tacacs_host
as TACACS host ipSet
authentication.tacacs_secret
as TACACS server secret
16.3. Testing Steps
16.3.1. Prerequisite for Testing
Ensure users are present in TACACS server, which can be used for authentication.
Configure OSM as mentioned above.
16.3.2. Testing
Login with credentials present in TACACS server.
OSM User with
system_admin
role or similar can assign project role mapping.TACACS users can log in using their credentials.
16.4. Limitations
Since TACACS is used as read-only service, username update and password update shall not be allowed via OSM. User credentials need to be updated by TACACS admin in TACACS to reflect. However, OSM admin can handle project role assignment as required.
If user profile is removed from TACACS server, OSM still maintains the profile and will not be removed until next login. As the profile is not available in TACACS, the authentication shall fail and user profile will be removed from OSM.