• TDS portal level
• TDS project level
• TDS project application level (Jira, Confluence, etc.)

Inviting users to TDS portal

Before user can be granted access to particular project he needs to be first invited and his account created.

If an admin wants to invite new user, he can do it by using  button under project Users tab. Once user receives to his email an invitation he can perform sign up and create his account. Now he will be able to log in to TDS portal.

Adding users to TDS project

Page Users shows the list of users connected with this Project. Project owner or admin can add already existing users to a Project using  button. If user is not in Customer area than he/she can be invited directly from add user modal window (as described in above). 

Once user is granted access to TDS project and can be found among all project Users.

If you want a new user to have access to all SaaS applications for your project tick the option Add to all services when inviting the user. 

There are 3 types of users:

• user - common user of Project
• admin - main Project administrator
• billing - activates page Billing

Adding user to project SaaS application(s)

Once user is member of project he can be granted user / administrator access to one or more SaaS application as JIRA, Confluence, Git, etc. Project admin / owner can add user to particular application using  button available for each application under left menu tab SaaS.

Project owner can edit or remove users by clicking on REMOVE.

Logs and graphs

Resources page contains information about the project's resources. Project owners can request change of resources by contacting support using Help Center.

Users can show usage statistics using Usage in the menu.

Item Logs opens page with detailed statistics about project.

Generating a SSH Key in a Windows

1. Download Putty Key Generator
2. Run the program and click on Generate and move your mouse (within the SSH generator window) until key is generated
   
   
3. Change Key comment to your Tieto email address in format name.surname@tieto.com
4. Optional: fill Key passphrase and confirm passphrase if you need one.
   If you skip this step then you need to confirm that you want to save the keys without passphrase in the next steps.
5. Save public key as id_rsa.pub
6. Save private key as id_rsa.ppk
   
7. From the top menu in Conversions select Export OpenSSH Key and save it as id_rsa
   Note that id_rsa.pub is your public key and can be shared, while id_rsa is your private key and should be kept secret.
   
   
8. Copy content of "Public key for pasting into OpenSSH authorized_keys file"
   
   
9. Go to the Portal and click on you name and then on SSH and then click on Add or change key
10. Paste copied key from the step 8. Click on the Save button.

Generating a SSH key on Linux

1. From the Terminal or Git Bash, run ssh-keygen
2. Confirm the default path .ssh/id_rsa
3. Enter a passphrase (recommended) or leave it blank.
   Remember this passphrase, as you will need it to unlock the key whenever you use it.
4. Open ~/.ssh/id_rsa.pub and copy & paste the contents into the box below, then click on "Add".
   Note that id_rsa.pub is your public key and can be shared, while id_rsa is your private key and should be kept secret.
5. Go to TDS portal and click on your name and then in left menu on SSH and then on Add or change key
6.  Paste the SSH key and click on the Save button.

Once you upload an SSH key it will be used on newly created server for authentication.

Converting SSH Keys to PPK Format

1. Download PuTTY Key Generator
2. Open the program and click on Conversion in top menu. Then choose Import key.
   
3. Locate your key in your computer and click open.
4. Once the key is loaded, you can save it as PPK file by clicking on Save Private Key or on Save Public Key if you want public version of your key.
   

Connecting to server using PuTTy for Windows

You'll need a SSH key. How to generate is described in this article.

PuTTy for Windows can be downloaded from this link. 

You can find a guide for using PuTTy for Windows at this link.

What desktop remote access client do you recommend?

Currently X2GO is the only supported client for Linux servers. Download X2GO client here.

To connect to Windows server please use Microsoft Remote Desktop or Remmina.

What operation system is supported by X2GO desktop remote access client?

Client X2GO is supported by Microsoft Windows, Apple Mac OS X, Ubuntu/Debian, Raspbian, Fedora, Redhat and FreeBSD. Download sources for manual installation here.

How to use X2GO client?

For user manual please use documents on a X2Go website.

Can I use Microsoft Remote Desktop?

Yes, but only for Windows-based virtual servers.

How to connect to Windows server from a Linux workstation?

You can use Remmina remote desktop application for Linux and other Unixes. For more information please visit a product website.

What is Remmina client?

Remmina is a free and open-source remote desktop client written in GTK+ and supports multiple network protocols in an integrated and consistent user interface. Currently RDP, VNC, NX, XDMCP and SSH are supported. For more information please visit product website.

Supported browsers

• We are recommending desktop variant of Google Chrome (version 40 and above).
• Mozilla FireFox (version 35 and above) is also supported.
• Support for Microsoft Internet Explorer 11 and Microsoft Edge is limited.
  
• Other browsers are not supported. 

Supported resolution

• XGA (1024 × 768) and HD (1280 × 720) on projectors
• WXGA (1280 × 800 and 1366 × 768) on laptops
• All common desktop resolutions including WSXGA+ (1680 × 1050), UXGA (1600 × 1200), FullHD (1920 × 1080) and higher

Virtual Environment Ubuntu screen is freezing randomly while using X2Go

Besides possible performance issues this can by caused by incompatibility of sound card. It can be solved by disabling audio support in X2Go - Session > Preferences > Media > Sound support

Closed remote proxy connection

It may happen that you can get following message when trying to connect to remote desktop. 

Workaround 1

Initial workaround is to remove all opened sessions from your local ~/.x2go directory:

rm -f ~/.x2go/S-*

When connecting to server remember to terminate old session(s) and start a new session.

Workaround 2

If workaround 1 did not help:

• repeat workaround 1 to avoid sessions mess

• login to your x2go remote server and remove .Xauthority file in your home directory on the remote server:

  rm -f ~/.Xauthority

• try X2go again

Workaround 3

If workaround 1+2 did not help:

• repeat workaround 1+2 to avoid sessions mess

• login to your x2go remote server and remove .ICEauthority file in your home directory on the remote server:

  rm -f ~/.ICEauthority

• try X2go again

Wrong version or invalid session authentication cookie

Symptoms

Message in x2go log while connecting to server:

Loop: PANIC! The remote NX proxy closed the connection.
Error: The remote NX proxy closed the connection.
Loop: PANIC! Failure negotiating the session in stage '7'.
Error: Failure negotiating the session in stage '7'.
Loop: PANIC! Wrong version or invalid session authentication cookie.
Error: Wrong version or invalid session authentication cookie.

This seems to occur sometimes after reboot of server while some users were still connected.

Workaround

• login to your x2go remote server via ssh and remove +re-create x2go sessions database file in your home directory on the remote server:

  rm -f /var/lib/x2go/x2go_sessions
  x2godbadmin --createdb

• try X2go again

Inspired by https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=323