Prequisites
To use nevisAdmin 4 in your environment, the software has to be installed first.
It is recommended starting with one of these variants:
Installation with Azure OneClick
- Make sure you have a Nevis Portal account. More information on how to create and manage your Nevis Portal account can be found here.
- Make sure you have access to an Azure Subscription with the following permissions:
- User Access Administrator or higher
- Contributor or higher
- Log in to your Azure subscription.
- Access Nevis Portal, select the "Deploy to Azure" button.
- Select your Azure subscription.
- Create a new resource group and name it.
- Select the region you wish to install to.
- Create a Domain name, and passwords for nevisAdmin4 and Grafana.
- Select "review + create" or review/change the default settings.
Observe that administration of the deployment COULD be pointed to an Azure SAML Identity Provider configuration which allows Azure-defined authentication mechanisms and policies to be used for authentication via a federated SAML connection. This would be instead of using local username/password credentials within the Nevis Identity Suite application.
- Note the summary and push "Create".
nevisAppliance installation with 2 VMs:
- VM1 with an admin4 image, version 2019-02-20 or later. See Software Installation for image and nevisAdmin 4 installation instructions.
- VM2 with the extended image, version 2019-02-20 or later. This image contains nevisProxy, nevisAuth, nevisIDM, and other components. See Software installation in the nevisAppliance documentation for image installation instructions.
We recommend using remote VMs instead of installing them on the same laptop. The reason is that it can be hard to configure the required networking/routing settings in VirtualBox or VMWare Workstation.
RPM-based installation, all on the same VM:
- Start with a basic RHEL 7 VM installation.
- See "Software Installation" for RPM and nevisAdmin 4 installation instructions.
- Install the RPM for nevisProxy 3.14.0.1 or higher.
For the tutorial below, it is assumed that:
nevisAdmin 4 is up and running, and reachable via
http://nevisadmin4:9080/nevisadmin/
.nevisProxy, or the nevisAppliance extended image, is installed
- The host is accessible via SSH at nevisproxy.
- After completing the tasks below, it will host a website at
https://nevis
.
Naming conventions
Depending on your environment, adapt the host names "nevisadmin4", "nevisproxy" and "nevis" as follows:
nevisAppliance installation:
- "nevisadmin4": Hostname of VM1.
- "nevisproxy": Hostname of VM2.
- "nevis": Hostname of VM2.
- Or: Add "nevis" to /etc/hosts on VM2 and on the device where the browser runs.
RPM-based installation, all on the same VM:
- "nevisadmin4": Hostname of the VM.
- "nevisproxy": Hostname of the VM.
- "nevis": Hostname of the VM.
- Or: Add "nevis" to /etc/hosts on the VM and on the device where the browser runs.