What is local user management?

Introduction

The NSP uses Keycloak-based OAUTH2 user authentication, which supports locally defined users for NSP access. If the NSP is integrated with NFM-P, you can also import the NFM-P users to the NSP local user database. Remote authentication agents are also supported.

Note: NSP Users and Security supports up to 5000 users.

For all local and remote users, the Users and Security GUI lists information that includes the authentication source, the user creation time, and the most recent login time.

Local user accounts can be used for machine-to-machine interaction, rather than creating user accounts in your corporate user database. They also provide a backup mechanism for cases where NSP cannot communicate with the corporate user database.

Migration from deprecated CAS authentication

Note: Support for the legacy CAS authentication mode is deprecated, and is to end in an upcoming release.

Migration from the legacy CAS authentication mode to OAUTH2 is strongly recommended, and is to be mandatory when CAS support is discontinued. During the migration to an integrated NSP and NFM-P deployment, you can import the NFM-P users to the NSP local user database.

Note: The WS-NOC supports only the legacy CAS authentication.

Note: Unlike CAS, OAUTH2 does not defer authentication to the NFM-P.

See “To migrate from CAS to OAUTH2 NSP user authentication” in the NSP Installation and Upgrade Guide for more information.