Ninja artifacts
Ninja artifacts are delivered as ZIP archive ninja-<version>.zip, because they depend on each other like other Nevis artifacts; for example jcan-sectoken, jcan-saml and additional third party dependencies. The zip provides all Nevis artifacts and pom files which allow integration of these artifacts into a maven or gradle build system. You can use the add-dependencies-to-maven-repo.sh in the zip file to deploy the artifacts to your local maven repository. In gradle you can add mavenLocal() to the repositories to access the local maven artifacts.
Ninja supports 3 token formats:
- SecToken
- SAML Assertion
- JWT bearer token (preview)
In order to support SAML assertions Ninja requires jcan-saml and jcan-saml-xmlbeans. Note that these jcan-saml libraries have a significant number of dependencies. In case you do not require support for SAML Assertions you do not need to include those in your application which can greatly reduce the number of dependencies required by Ninja. By default, Nevis adds the SAML libraries to support all features out of the box.
JWT bearer token authentication is built into ninja-commons via the nevis-jwt library. No additional JARs are needed beyond the standard Ninja dependencies. See JWT Authentication for configuration details.
The delivery approach provides the flexibility to override dependency versions during integration.
Nevis is testing Ninja with the dependency versions present in the shipped pom.xml files. Nevis cannot warrant the components proper behaviour in case the dependency versions are changed during integration.