Infra:connection: Difference between revisions
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 8: | Line 8: | ||
This documentation page explains these steps. | This documentation page explains these steps. | ||
== Gitlab == | |||
=== Connection === | |||
In order to connect to gitlab, go to forge.infosec.unamur.be and click on the "Infosec" button, under the connection form. | In order to connect to gitlab, go to forge.infosec.unamur.be and click on the "Infosec" button, under the connection form. | ||
In the connection form that appears, you should be able to use your UNamur credentials. | In the connection form that appears, you should be able to use your UNamur credentials. | ||
Note that your UNamur username have to be added in the system by an administrator of the platform before. Otherwise, your connection attempt will be rejected. | |||
''Note that your UNamur username have to be added in the system by an administrator of the platform before. Otherwise, your connection attempt will be rejected.'' | |||
=== After the first connection === | |||
When you first connect to gitlab, you have to make some modifications to your profile : | When you first connect to gitlab, you have to make some modifications to your profile : | ||
1. Add your UNamur (preferably) or another valid email address to your account and confirm it. | 1. Add your UNamur (preferably) or another valid email address to your account and confirm it. | ||
2. Go to "Emails" section of your profile and remove the email that have the format : temp-email-for-oauth-USERNAME@gitlab.localhost | 2. Go to "Emails" section of your profile and remove the email that have the format : temp-email-for-oauth-USERNAME@gitlab.localhost | ||
3. Add you SSH public key to your profile (you will not be able to pull or push to repositories otherwise) | 3. Add you SSH public key to your profile (you will not be able to pull or push to repositories otherwise) | ||
Nextcloud | |||
Connection | == Nextcloud == | ||
=== Connection === | |||
In order to connect to gitlab, go to hub.infosec.unamur.be and click on the "UNamur account" button, under the connection form. | In order to connect to gitlab, go to hub.infosec.unamur.be and click on the "UNamur account" button, under the connection form. | ||
In the connection form that appears, you should be able to use your UNamur credentials. | In the connection form that appears, you should be able to use your UNamur credentials. | ||
Note that your UNamur username have to be added in the system by an administrator of the platform before. Otherwise, your connection attempt will be rejected. | |||
Using the mobile or desktop synchronisation client | ''Note that your UNamur username have to be added in the system by an administrator of the platform before. Otherwise, your connection attempt will be rejected.'' | ||
=== Using the mobile or desktop synchronisation client === | |||
When you try to set up the synchronisation client, it asks you a username and a password. It's worth noting that in this situation, your UNamur username and password will not work. So to be able to use the desktop or mobile synchronisation client, follow these steps : | When you try to set up the synchronisation client, it asks you a username and a password. It's worth noting that in this situation, your UNamur username and password will not work. So to be able to use the desktop or mobile synchronisation client, follow these steps : | ||
1. Connect to hub.infosec.unamur.be | 1. Connect to hub.infosec.unamur.be | ||
2. Go to your profile and under security tab | 2. Go to your profile and under security tab | ||
3. Create an application password | 3. Create an application password | ||
4. Save the username and password given | 4. Save the username and password given | ||
5. Use this credentials in the synchronisation client | 5. Use this credentials in the synchronisation client | ||
Latest revision as of 13:47, 22 February 2019
Our team disposes of several collaborative tools :
- A gitlab (forge.infosec.unamur.be)
- A nextcloud (hub.infosec.unamur.be)
- A wiki (doc.infosec.unamur.be)
When an administrator of the team (the teaching assistant or the professor) added you in our centralized authentication, you will be able to connect to all of these tools using your UNamur credentials. However Forge and hub necessitate several additional steps in order for you to use them correctly. This documentation page explains these steps.
Gitlab
Connection
In order to connect to gitlab, go to forge.infosec.unamur.be and click on the "Infosec" button, under the connection form. In the connection form that appears, you should be able to use your UNamur credentials.
Note that your UNamur username have to be added in the system by an administrator of the platform before. Otherwise, your connection attempt will be rejected.
After the first connection
When you first connect to gitlab, you have to make some modifications to your profile :
1. Add your UNamur (preferably) or another valid email address to your account and confirm it.
2. Go to "Emails" section of your profile and remove the email that have the format : temp-email-for-oauth-USERNAME@gitlab.localhost
3. Add you SSH public key to your profile (you will not be able to pull or push to repositories otherwise)
Nextcloud
Connection
In order to connect to gitlab, go to hub.infosec.unamur.be and click on the "UNamur account" button, under the connection form. In the connection form that appears, you should be able to use your UNamur credentials.
Note that your UNamur username have to be added in the system by an administrator of the platform before. Otherwise, your connection attempt will be rejected.
Using the mobile or desktop synchronisation client
When you try to set up the synchronisation client, it asks you a username and a password. It's worth noting that in this situation, your UNamur username and password will not work. So to be able to use the desktop or mobile synchronisation client, follow these steps :
1. Connect to hub.infosec.unamur.be
2. Go to your profile and under security tab
3. Create an application password
4. Save the username and password given
5. Use this credentials in the synchronisation client