Please note the following CATCH-22 set up problem on current (and previous) releases. I found the following problem which is is simple catch 22 issue Having de-installed TB beta - I tried to intall the latest SR version. However the Standard set-up tool does not support OAuth2 in its options list. So if the target server employs OAuth2 one can never effect a direct connection with the server automatically. Moving to the manual option reveals the same problem -same option list. One has to move to ''advanced configuration'' and save with the wrong settings and then edit them . It is not clear anywhere that this is required. The dialogue is not enough and what little is there is not helpful. The set-upl should move there automatically on a first automatic connection failure. ''[or more sensibly just add OAuth2 to the dialogue box]". I did not realise that I had to move to the advanced configuration at first. So I gave up. [I had gone throught this loop previously in Sept 2020 and given up too]. It was only later that I thought to go back and check what was in "Advanced". This set should be a breeze but the logic is flawed and the terms are mistitled. The same problem arises in setting up a Beta version. Can you please improve this for users. Gilbert .