This is v9.4 of the developer resources that can be found under Start, Develop, Deploy, Operate, Customize and Reference sections, except with references to the Nok Nok S3 Suite instead of the DigipassONE Platform.

Server Tarball Contents

Prev Next

Server Install File

The install file, nn3_server_package_<version>.tgz contains the following artifacts:

  • Pre-install check script

  • Server installation scripts and deployables

  • Post-install check script

  • App SDK emulator for FIDO UAF and FIDO2/WebAuthn

The following artifacts of the Huawei Messaging Service (HMS) are not included in nn3_server_package_<version>.tgz:

  • hms-push.jar

  • nnl-hms-artifacts-*.jar

  • license file

  • Huawei FIDO2 Authenticator metadata

To request these files, please contact support@noknok.com.

Below is a high-level, abridged version of the tarball contents.

Scripts nnl-preinstall-checks.sh and nnl-postinstall-checks.sh were deprecated. nnl-install.sh performs these functions. See Step 2. Verify That Your Server is Ready for Installation and Step 7. Verify the Installation.

./mfas
├── install
│   ├── internal
│   │   ├── ...
│   │   └── (Supporting scripts and other files)
│   ├── ...
│   ├── nnl-encrypt-password.sh
│   ├── nnl-install.properties
│   ├── nnl-install.sh
│   ├── nnl-key-generator.sh
│   ├── nnl-uninstall.sh
│   └── tenants 
│       ├── Admin (Configuration files for Admin tenant)
│       │   ├── apiserver
│       │   │   ├── Main
│       │   │   └── Main.json
│       │   ├─── properties
│       │   └─── nnl-admin-runtime.properties
│       ├── Admin.zip
│       ├── default  (Configuration files for default tenant)
│       │   ├── apiserver
│       │   │   ├── Main
│       │   │   └── Main.json
│       │   ├── properties
│       │   └── nnl-default-runtime.properties
│       ├──  default.zip
│       └──  Tenant-Creation-README
├── licenses
│   └── (Third-party software license files)
├── version.txt (Contains product version number)
├── artifact-versions.txt
└── admin (See the next structure for details)

The admin directory has the following structure:

      admin
        ├── bin
        │    ├── nnl-classpath.sh
        │    ├── nnl-key-generator.sh
        │    ├── nnl-mgmt.sh
        │    ├── nnl-um
        │    │    └── lib (authsvc, nnlgateway, and third-party jars)
        │    └── internal
        │         ├── PostInstallCheck
        │         └── scripts
        │              ├── nnl-env-variables.sh
        │              ├── nnl-install-common.sh
        │              ├── nnl-install-constants.sh
        │              ├── nnl-install.properties
        │              ├── nnl-logger.sh
        │              └── scripts-log4j2.xml
        ├── conf
        │    ├── application.properties
        │    ├── log4j2.xml 
        │    ├── nnladmin (configuration files for the CLI)
        │    ├── nnl-db.properties
        │    └── nnl-java-security.properties
        ├── lib (nnl and third party jars)
        └── tool
             └── Testclient
                  ├── webEmulator.sh
                  ├── webclient.properties
                  ├── runEmulator.sh
                  ├── runClient.sh
                  ├── lib (nnl and third party jars)
                  ├── licenses
                  ├── uaf (UAF test data)
                  └── webauthn (WebAuthn test data)

App SDK Emulator

The App SDK Emulator is located at <NNL_HOME>/admin/tool/Testclient. This tool emulates the App SDK so you can test the V2 REST API by creating a request payload and post to the endpoint and operation. The tool supports both FIDO UAF and FIDO2/WebAuthn protocols. If you plan to use the App SDK Emulator, contact Support for the App SDK Emulator Tech Note and WebAuthn Emulator Tech Note.