About this Document
The Nevis Mobile Authentication Concept and Integration Guide serves as an overall guide to the Nevis Mobile Authentication Solution for interested parties. It focuses on the server side of the solution.
The guide consists of the following sections:
Section | Description |
---|---|
Overview | This chapter gives an overview of Nevis Mobile Authentication, the problems it solves and what basic use cases it supports. |
Concept Description | This chapter describes the basic concepts and principles of FIDO UAF 1.1 and Nevis Mobile Authentication. |
Technical Architecture | The technical architecture section shows the technical elements of the solution as well as how these elements interact with each other and with their environment. |
Installation | The installation section focuses on the system requirements as well as intended deployment scenarios for the Nevis Mobile Authentication solution. |
Configuration | The configuration section serves as a collection of the different involved component configuration references. |
Use Cases and Best Practices | Step-by-step instructions and explanations for common use cases and selected special use cases. Apart from high-level explanation of the use cases, more detailed explanation including configuration instructions and technical implementation details are included. |
Security Considerations | The security considerations section lists Nevis Mobile Authentication specific security related topics. |
FAQ | Unstructured collection of commonly posed questions. Readers are expected to read this as a reference. This chapter will grow over time as more questions and will answer will be identified based on feedback. |
Glossary | Definition of commonly used terms in Nevis Mobile Authentication. |
Apart from the Concept and Integration Guide, the Reference Guides provide in-depth technical information regarding the installation, integration, configuration, administration and operation of the components that compose the Nevis Mobile Authentication Solution. This includes the HTTP APIs.