Ubuntu est la plateforme que nous recommandons pour les nouvelles installations de l’appliance Notakey. Les versions actuelles de l’appliance (5.0.87 au moment de la rédaction) s’installent également sur Debian, Fedora et CentOS, à condition que Docker y soit installé. RancherOS, la plateforme d’origine de l’appliance, est obsolète : elle n’est plus prise en charge que pour maintenir en fonctionnement les appliances existantes, jamais pour un nouveau déploiement.
-
Installez une VM Ubuntu avec le serveur OpenSSH. Choisissez une version LTS encore prise en charge.
-
Installez Docker : https://docs.docker.com/engine/install/ubuntu/
-
Ajoutez votre utilisateur au groupe docker :
sudo usermod -aG docker $USER- Désactivez cloud-init et redémarrez :
sudo touch /etc/cloud/cloud-init.disabled
sudo init 6- Lancez l’installateur de l’appliance Notakey :
docker run -it \
--privileged \
--net=host \
-e NTK_USER=root \
-v /var/run/docker.sock:/var/run/docker.sock:rw \
-v /:/appliancehost \
notakey/cfg:latest installL’installateur vous guide tout au long de la configuration :
_______ __ __
\ \ _____/ |______ | | __ ____ ___.__.
/ | \ / _ \ __\__ \ | |/ // __ < | |
/ | ( <_> ) | / __ \| <\ ___/\___ |
\____|__ /\____/|__| (____ /__|_ \\___ > ____|
\/ \/ \/ \/\/
Welcome to the Notakey Authentication Appliance
installation wizard.
This wizard will install required utilities for appliance
management.
Do you wish to continue? (y/n): y
==> Detecting OS
Detected Ubuntu 20.04
==> Determining user
Running as root
==> Creating directories
==> Installing management utilities
==> Config already exists, skipping
==> Storing version information
==> Checking required cli version
install: notakey/cfg:5.0.55
running: notakey/cfg:latest
tagging: notakey/cfg:5.0.55
==> Storing configuration
==> Installing ntk cli wrapper
==> Symlinking ntk cli
==> Updating $PATH
==> Configuring assets directory
Assets stored in /opt/notakey/shared
Edit /opt/notakey/cfg/.env to adjust
==> The following package versions will be downloaded
downloading all latest packages
cli: naa/cfg:5.0.55 (exclusive update)
dashboard: naa/auth-server:4.0.32
auth-proxy: naa/auth-proxy:1.0.8
consul: naa/consul:1.9.9
traefik: naa/traefik:1.7.33
vrrp: keepalived:2.1.5-1
sso: naa/sso-server:3.4.7
redis: naa/redis:6.2.5
cron: naa/deck-chores:1.2.0
==> Downloading from repo.notakey.com
downloading naa/cfg:5.0.55
downloading naa/auth-server:4.0.32
downloading naa/auth-proxy:1.0.8
downloading naa/consul:1.9.9
downloading naa/traefik:1.7.33
downloading keepalived:2.1.5-1
downloading naa/sso-server:3.4.7
downloading naa/redis:6.2.5
downloading naa/deck-chores:1.2.0
==> Configuration update
update complete
Do you wish to run configuration wizard? (y/n): y
==> Gathering informationLes versions des composants reproduites ici sont celles qu’a téléchargées la session enregistrée. Votre installation récupérera quant à elle les versions en vigueur au moment où vous la lancerez.
- Suivez la documentation de configuration de l’appliance tout au long de l’assistant :
NOTE: Node hostname must be unique within cluster and
must contain only alphanumeric characters and -
with no other punctuation or spaces.
Enter the node hostname [ntknode]:
NOTE: Datacenter / domain must be the same if assembling
local multi node cluster. Local cluster resides in
single LAN segment with unrestricted communication.
This value must contain only alphanumeric characters
and - with no other punctuation or spaces.
Enter the cluster datacenter name/local domain [dc]:
NOTE: You can specify below to join automatically an existing
cluster. Specifying y will start cluster locally and
attempt to join existing cluster by connecting to
specified IP address. Cluster service must be started on
remote host and must be in healthy state.
If unsure, say n, you will have a chance to do this later.
Are you joining existing cluster? (y/n) [n]:
NOTE: FQDN below is used for SSL termination and will be
used for all mobile clients to connect to this service.
This is not the hostname of this node in cluster.
Usually looks like 'mfa.example.com' where 'example.com'
would be your organizations domain name
Enter the desired main FQDN for NAS API []: test.notakey.com
Enter internal cluster advertise IPv4 address [192.168.66.71]:
Use builtin reverse proxy for TLS termination? (y/n) [y]:
Use automated TLS certificate setup (Let's Encrypt?) (y/n) [n]: y
Enter e-mail address to use for requesting TLS certificate []: admin@me.com
==> Please review the entered information
Node name: ntknode
Datacenter: dc
External domain: test.notakey.com
Cluster node address: 192.168.66.71
Use Let's Encrypt (automatic SSL): y
E-mail for Let's Encrypt: admin@me.com
Are these values OK? (y/n): y
==> Applying configuration
acme... ok
default configuration... ok
starting cluster service... done (restart)
waiting for cluster startup... ok
host... ok
cluster config... ok
==> WIZARD DONE
Next steps:
1. Reboot the appliance with 'ntk sys reboot' command
2. Call 'ntk as start' to launch core authentication service
Optionally:
- Use 'ntk vrrp ...' commands to configure IP failover
- Use 'ntk sys ntp 1.2.3.4' to configure NTP service
- Use 'ntk sys timezone Europe/Rome' to configure timezone
- Use 'ntk backup ...' commands to backup/restore configuration
- Use 'ntk sys update' command to update to latest version
Please visit http://docs.notakey.com for detailed instructions