Skip to Content

Changes for page 2. Automated Sign-in

Last modified by teamwire001 on 2025/10/28 13:49
From version 6.2
edited by teamwire001
on 2025/08/19 08:12
Change comment: DOC-434
To version 7.1
edited by teamwire001
on 2025/10/28 13:49
Change comment: Imported from XAR

Summary

Details

Page properties
Content
... ... @@ -34,7 +34,10 @@
34 34  Please comment out parameters that are not required, e.g. ##ProxyURL##.
35 35  )))
36 36  
37 +(% style="border-color:var(--gili_blue_300)" %)
38 +----
37 37  
40 +
38 38  {{id name="macosandlinux"/}}
39 39  
40 40  = macOS and Linux =
... ... @@ -68,7 +68,10 @@
68 68  Please delete the parameters that are not required, e.g. ##ProxyURL##.
69 69  )))
70 70  
74 +(% style="border-color:var(--gili_blue_300)" %)
75 +----
71 71  
77 +
72 72  {{id name="mandatory"/}}
73 73  
74 74  = Mandatory parameters =
... ... @@ -95,7 +95,10 @@
95 95  * ##BackendServerName##: Teamwire Server name as described in [[Advanced Configurations>>doc:Public.Applications.Desktop.Advanced-Configurations.WebHome||anchor="4-hostname"]] (optional but recommended)
96 96  )))
97 97  
104 +(% style="border-color:var(--gili_blue_300)" %)
105 +----
98 98  
107 +
99 99  {{id name="securityadvice"/}}
100 100  
101 101  = Security advice =
... ... @@ -102,6 +102,6 @@
102 102  
103 103  The registration token is a very sensible piece of information and needs to be protected against the access of unauthorised persons. We recommend to keep the channel you use, for transmitting the token to the desktop computers, as safe as possible. The file should be also saved with the most restrictive permissions.
104 104  
105 -Do not use your organisation's registration token to sign in desktop users. One-time registration tokens for each individual user can be used in parallel, and are much safer since the Windows Registry and configuration files can be examined by users. Therefore the user may abuse the organisation's token and sign in any Teamwire user account. For details about the one-time registration token, please refer to the section about [[User operations>>doc:Customer.Administration.Dashboard-User-Manual.Users.WebHome||anchor="users-useroperations"]] in the [[Dashboard manual>>doc:Customer.Administration.Dashboard-User-Manual.WebHome]].
114 +Do not use your organisation's registration token to sign in desktop users. One-time registration tokens for each individual user can be used in parallel, and are much safer since the Windows Registry and configuration files can be examined by users. Therefore the user may abuse the organisation's token and sign in any Teamwire user account. For details about the one-time registration token, please refer to the section about [[User operations ( {{icon name="sign-in" size="1x" cssClass="fa-blue helpc" title="This document is only available to logged-in users"/}})>>doc:Customer.Administration.Dashboard-User-Manual.Users.WebHome||anchor="users-useroperations" title="This document is only available to logged-in users"]] in the Dashboard Manual.
106 106  
107 107  ## ##
teamwire-windows.reg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.teamwire001
Size
... ... @@ -1,0 +1,1 @@
1 +3.3 KB
Content
... ... @@ -1,0 +1,97 @@
1 +��Windows Registry Editor Version 5.00
2 +
3 +
4 +
5 +[HKEY_CURRENT_USER\SOFTWARE\teamwire]
6 +
7 +
8 +
9 +; FIRST NAME
10 +
11 +; Mandatory for automated registration
12 +
13 +; The user's first name
14 +
15 +; Uncomment the following line to use this setting:
16 +
17 +;"firstName"="USER_FIRST_NAME"
18 +
19 +
20 +
21 +; LAST NAME
22 +
23 +; Mandatory for automated registration
24 +
25 +; The user's last name
26 +
27 +; Uncomment the following line to use this setting:
28 +
29 +;"lastName"="USER_LAST_NAME"
30 +
31 +
32 +
33 +; EMAIL ADDRESS
34 +
35 +; Mandatory for automated registration
36 +
37 +; The user's email address
38 +
39 +; Uncomment the following line to use this setting:
40 +
41 +;"email"="USER_EMAIL"
42 +
43 +
44 +
45 +; REGISTRATION TOKEN
46 +
47 +; Mandatory for automated registration
48 +
49 +; The user's one-time registration token
50 +
51 +; Uncomment the following line to use this setting:
52 +
53 +;"registrationToken"="TOKEN"
54 +
55 +
56 +
57 +; PHONE NUMBER (optional)
58 +
59 +; Phone number in the user's profile
60 +
61 +; Uncomment the following line to use this setting:
62 +
63 +;"phoneNumber"="PHONE_NUMBER"
64 +
65 +
66 +
67 +; TEAMWIRE SERVER HOSTNAME (optional)
68 +
69 +; Do not include protocol like https://
70 +
71 +; Default hostname is "backend.teamwire.eu"
72 +
73 +; Uncomment the following line to use this setting:
74 +
75 +;"serverHost"="CUSTOM_SERVER_HOSTNAME"
76 +
77 +
78 +
79 +; PROXY URL (optional)
80 +
81 +; The proxy URL should contain the protocol, user (if any), server name and port
82 +
83 +; Uncomment the following line to use this setting:
84 +
85 +;"proxyUrl"="COMPLETE_SERVER_PROXY_URL"
86 +
87 +
88 +
89 +; TRUSTED CERTIFICATES (optional)
90 +
91 +; Whitelist your self-signed certificate(s), separated by spaces. The certificates need to be base64-encoded SHA256 certificate fingerprints.
92 +
93 +; Uncomment the following line to use this setting:
94 +
95 +;"trustedCertificates"="FIRST_FINGERPRINT SECOND_FINGERPRINT"
96 +
97 +
teamwire.cfg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.teamwire001
Size
... ... @@ -1,0 +1,1 @@
1 +237 bytes
Content
... ... @@ -1,0 +1,11 @@
1 +{
2 +"firstName": "String",
3 +"lastName": "String",
4 +"email": "String",
5 +"registrationToken": "String",
6 +"phoneNumber": "String",
7 +"serverHost": "String",
8 +"proxyUrl": "String",
9 +"trustedCertificates": ["FIRST_FINGERPRINT", "SECOND_FINGERPRINT"]
10 +}
11 +