Differences

This shows you the differences between two versions of the page.

--- gitlab_notes [2022/03/28 08:18] – [Remote repo to local file system] lenocil
+++ gitlab_notes [2022/08/09 12:02] (current) – [Gitlab Notes] lenocil
@@ Line 1: / Line 1: @@
 ====== Gitlab Notes ======
+Lorentz Institute runs a private instance of Gitlab accessible to all institute members available at https://gitlab.lorentz.leidenuniv.nl regardless of their role within the Institute. You are strongly encouraged to use it to collaborate with your colleagues and fellow scientists anywhere in the world.
-|IMPORTANT\\ :!:|Gitlab logins via the Lorentz Institute IdP might assign you a gitlab username different than expected.\\ Please check https://gitlab.lorentz.leidenuniv.nl/-/profile/account and do **not** change it\\ ssh  -T git@gitlab.lorentz.leidenuniv.nl will also return your gitlab username|
+Accounts for external users can be requested via <support@lorentz.leidenuniv.nl>.
-Lorentz Institute runs a private instance of Gitlab accessible to all institute members at https://gitlab.lorentz.leidenuniv.nl regardless of their role within the Institute.
+Lorentz Institute members login using the button  //Sign in with Lorentz Institute IdP// via the institute Identity Provider Server, where as external users, after their access has been approved and account created,  will login via //Standard// tab in the authentication form. See figures below
-You are strongly encouraged to use it to collaborate with your colleagues and fellow scientists anywhere in the world. Accounts for external users can be requested via <support@lorentz.institute.nl>.
-Lorentz Institute members **must use** the button  //Sign in with Lorentz Institute IdP// to login via the institute Identity Provider Server, where as external users must use the //Standard// tab in the authentication form.
 {{::gitlab1.png?nolink&300|}}  {{:gitlab2.png?nolink&200|}}
@@ Line 13: / Line 10: @@
 ===== SSH Keys and Personal Access Tokens =====
-Because access to the Institute Gitlab instance occurs via Single-Sign On((In other words it uses access and refresh tokens rather than usernames and passwords)) for all IL members, git //push// and //pull// operations must be performed either using __SSH key-pairs__ (SSH protocol) or using __Personal Access Tokens__ (HTTPS protocol). Failing to set up SSH key-pairs or Access Tokens will prevent IL members to interact via git with our Gitlab server.
+Because access to the Institute Gitlab instance occurs via Single-Sign On((In other words it uses access and refresh tokens rather than usernames and passwords.)) for all IL members, git //push// and //pull// operations must be performed either using __SSH key-pairs__ (SSH protocol) or using __Personal Access Tokens__ (HTTPS protocol). Failing to set up SSH key-pairs or Access Tokens will prevent IL members to interact via git with our Gitlab server.
 IL users that do not set up SSH key-pairs or Access Tokens will likely receive upon login a warning message like the one in the figure below
@@ Line 43: / Line 40: @@
 {{ :gitlab6.png?nolink&600 |}}
-Your personal access token will look something like ''xyzop-ybVxByblaUBLA7RUAGAs''((This is a fake one)). Please take note of it and store it in a very safe place. Disclosing this token is equivalent to disclosing your credentials! Should a token be compromised at any time, just visit  https://gitlab.lorentz.leidenuniv.nl/-/profile/personal_access_tokens to revoke any compromised tokens.
+Your personal access token will look something like ''xyzop-ybVxByblaUBLA7RUAGAs''((This is a fake one.)). Please take note of it and store it in a very safe place. Disclosing this token is equivalent to disclosing your credentials! Should a token be compromised at any time, just visit  https://gitlab.lorentz.leidenuniv.nl/-/profile/personal_access_tokens to revoke any compromised tokens.
 Your IL account is now enabled to perform git operations over //HTTPS//.

Computer Documentation Wiki

User Tools

Site Tools

Differences

Page Tools