@@ -37,7 +37,7 @@ Yes, when reestablishing the site-to-site VPN connection, it is very likely that
...
@@ -37,7 +37,7 @@ Yes, when reestablishing the site-to-site VPN connection, it is very likely that
### Can I continue to use the existing client-access VPN tunnels?
### Can I continue to use the existing client-access VPN tunnels?
No, once a given domain is migrated to the new infrastructure it is expected that all users that require access to the deployed applications within it will be using eduVPN as the client access VPN technology. Since eduVPN can use both Wireguard and OpenVPN behind the scenes, compatibility with all major computing platforms is guaranteed. The nmaas team has made this decision in order to simplify administration aspects, since the management of different overlapping client-access VPN solutions adds additional burden and is time-consuming.
No, once a given domain is migrated to the new infrastructure it is expected that all users that require access to the deployed applications within it will be using [eduVPN](https://eduvpn.nmaas.eu) as the client access VPN technology. Since eduVPN can use both Wireguard and OpenVPN behind the scenes, compatibility with all major computing platforms is guaranteed. The nmaas team has made this decision in order to simplify administration aspects, since the management of different overlapping client-access VPN solutions adds additional burden and is time-consuming.
### Will the URLs of my applications change?
### Will the URLs of my applications change?
...
@@ -48,3 +48,37 @@ No, the URLs will remain the same. E.g., if there is a Prometheus instance with
...
@@ -48,3 +48,37 @@ No, the URLs will remain the same. E.g., if there is a Prometheus instance with
The nmaas vNOC instance hosted on the new infrastructure will be accessible at [vnoc.nmaas.eu](https://vnoc.nmaas.eu). As part of the migration process, users will receive a personalized email when they will need to start using the [vnoc.nmaas.eu](https://vnoc.nmaas.eu) endpoint. Until that time, all activity is done via [https://nmaas.eu](https://nmaas.eu).
The nmaas vNOC instance hosted on the new infrastructure will be accessible at [vnoc.nmaas.eu](https://vnoc.nmaas.eu). As part of the migration process, users will receive a personalized email when they will need to start using the [vnoc.nmaas.eu](https://vnoc.nmaas.eu) endpoint. Until that time, all activity is done via [https://nmaas.eu](https://nmaas.eu).
Hosting the vNOC instance using the `vnoc` subdomain also goes hand-in-hand with the new nmaas branding strategy centered around the different use-cases - [vNOC](../../use-cases/virtual-noc/vnoc-introduction.md) and [vLAB](../../use-cases/virtual-lab/vlab-introduction.md).
Hosting the vNOC instance using the `vnoc` subdomain also goes hand-in-hand with the new nmaas branding strategy centered around the different use-cases - [vNOC](../../use-cases/virtual-noc/vnoc-introduction.md) and [vLAB](../../use-cases/virtual-lab/vlab-introduction.md).
### From where can I download a client-access VPN profile?
Client access VPN profiles can be downloaded from the eduVPN self-service portal available on [eduvpn.nmaas.eu](https://eduvpn.nmaas.eu). Logging in to the self-service portal is done with the same account as when accessing nmaas. If you are a member of multiple nmaas domains, you will be able to download a VPN profile for each domain.
The profiles downloaded from eduVPN can be used with any OpenVPN compatible client application or with the [official eduVPN client](https://www.eduvpn.org/client-apps/). A given user can generate multiple client-access profiles, for example for multiple devices (laptop, smartphone, workstation...).
### How can I login to the new instance?
The legacy [nmaas.eu](nmaas.eu) instance supported two different modes of authentication:
- local nmaas accounts
- federated login via eduGain
With the migration to [vnoc.nmaas.eu](vnoc.nmaas.eu) all accounts (both local and federated) have been migrated to a new authentication and authorization infrastructure. This will also enable to use the same login throughout the whole nmaas tools ecosystem, including the eduVPN self-service portal.
The conversion of existing accounts to the new authentication backend requires specific user action, depending on the type of the account, as explained below.
#### How can I login if I previously used a local account?
For users who logged in directly to [nmaas](https://nmaas.eu) using the built-in authentication form specifying their username and password, the following steps need to be perfromed upon their first login to [vnoc.nmaas.eu](https://vnoc.nmaas.eu):
1. Navigate to [vnoc.nmaas.eu](https://vnoc.nmaas.eu) and click on the Login button. Choose the `Federated Login` option. This will issue a redirect to [auth.nmaas.eu](https://auth.nmaas.eu)
2. Using the `Forgot your password` option, reset your password, providing the original email address that was used during the initial registration.
3. Using the password reset link that you should have received via an email message, set a new password.
4. You will be automatically redirected to [vnoc.nmaas.eu](https://vnoc.nmaas.eu) where you will be asked to merge your old account with your new one. All user data and domain associations will remain after the merging process is complete. The merging process is done by entering your email address and the password that you used for your original account on [nmaas.eu](https://nmaas.eu).
#### How can I login if I previously used a federated account?
For users who logged in directly to [nmaas](https://nmaas.eu) using the federated login option (via eduGAIN), the following steps need to be perfromed upon their first login to [vnoc.nmaas.eu](https://vnoc.nmaas.eu):
1. Navigate to [vnoc.nmaas.eu](https://vnoc.nmaas.eu) and click on the Login button. Choose the `Federated Login` option. This will issue a redirect to [auth.nmaas.eu](https://auth.nmaas.eu)
2. Click on the button `eduGAIN` and choose your institution from the list, as usually.
