Changes for page Announcements

Last modified by hbpadmin on 2025/01/09 12:12
From version 12.2
edited by hbpadmin
on 2021/02/17 13:37
Change comment: There is no comment for this version
To version 2.1
edited by mmorgan
on 2020/05/26 20:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.hbpadmin
1 +XWiki.mmorgan
Content
... ... @@ -1,65 +1,19 @@
1 -(% class="wikigeneratedid" %)
2 -== Collaboratory 2 release (2021-02-17) ==
1 +== Announcement ==
3 3  
4 -The release going ahead on 17th February has the following enhancements.
5 -
3 +On the 14th of May 2020, several High Performance Computing centres across Europe suffered a cyber-attack. The attack affected the infrastructure which hosts multiple HBP and EBRAINS services. As a precaution, and in order to ensure the continued security of the HBP and EBRAINS services, all users with an HBP and/or EBRAINS user account are requested to change their password, bot in Collaboratory 1 ([[https:~~/~~/collab.humanbrainproject.eu>>https://collab.humanbrainproject.eu]]) and Collaboratory 2 ([[https:~~/~~/wiki.ebrains.eu>>https://wiki.ebrains.eu]]).
6 6  
7 -1. Mounting a new "Shared" drive for the ability to easily share links from Seafile. So going forward, any links that need to be shared should be generated in the "Shared " drive. The original "/drive" will be kept so it does not break any of the already existing links.
8 -1. OnlyOffice is being upgraded to the latest version. This should solve the issue listed below in the "Files locked in the Drive " section. The section will remain temporarily until it is verified this solution is fully fixed.
9 -1. Seafile file system is being increased
5 +The current passwords were deactivated in Collaboratory 1 on May 26. Please request a new password by clicking //Forgot password// at the login prompt.
10 10  
11 -(% class="wikigeneratedid" %)
12 -== ==
7 +Users logging in to Collaboratory 2 starting May 27 will be asked to reset their password.
13 13  
14 -== Collaboratory 1 maintenance ==
9 +Select a password that you do not use on other accounts and that cannot be easily guessed by someone knowing your other passwords.
15 15  
16 -Collaboratory 1 services will be down from 18:00 CET [[(my timezone)>>https://everytimezone.com/s/4a9daa55]] Thursday Jan 7 for maintenance. The services are being re-hosted from the EPFL/BBP infrastructure to the Fenix infrastructure. The OIDC authentication service will be reactivated first (within 30 minutes); all other services will follow in the evening. Once the Collaboratory 1 services are back online, you may find that files added to the storage within the last days do not initially appear. This will be remedied overnight as we synchronize the storage. Thank you for your patience and understanding.
11 +Select a password sufficiently long and complex with a mix of lower case, upper case, digits and punctuation.
17 17  
18 -As a reminder the Collaboratory 1 services are deprecated and will be shut down in September 2021.
13 +Remember that you are responsible for protecting your password. Do not write your password in clear form.
19 19  
20 -If you encounter issues with Collaboratory 1 after Friday 12:00 CET, please contact [[https:~~/~~/ebrains.eu/support>>url:https://ebrains.eu/support]]
15 +Thank you for your cooperation.
21 21  
22 -(% class="wikigeneratedid" id="H" %)
23 -The re-hosting was completed on Thursday evening. Some services relying on the Collaboratory 1 may need to be restarted to take into account the new DNS entries. Please notify [[support>>https://ebrains.eu/support]] of any issues you identify.
17 +The Collaboratory team, updated May 26 2020
24 24  
25 -
26 -== SSL certificates (2020-12-04) ==
27 -
28 -Our SSL Certificate provider (Let's Encrypt) has been using new certificates to sign our SSL certificates as described on their [[website>>https://letsencrypt.org/certificates]]. This requires updates on our servers and on your web browsers. The updates on your web browsers often go unnoticed by the user but in some cases your browser may inform you that it needs to fetch a new certificate. You can accept this safely; most browsers don't even mention it to the user.
29 -
30 -Note that this is not the same as accepting an exception in your browser because of a bad certificate. Accepting such exceptions can put your data and credentials at risk of a person-in-the-middle attack.
31 -
32 -We believe we have addressed all the issues that may arise from this change in SSL certificates. If you experience any issue, especially when accessing EBRAINS APIs, don't hesitate to contact [[support>>https://ebrains.eu/support]].
33 -
34 -
35 -== Files locked in the Drive (2020-09-30) ==
36 -
37 -A few users have reported issues in saving OnlyOffice edits to the Drive of a collab.
38 -
39 -We are looking into this. At the time being, it seems that a small number of files are locked by the Drive which prevents OnlyOffice to update these files when they are edited online.
40 -
41 -We are actively trying to correct the problem as promptly as possible.
42 -
43 -==== The temporary workaround ====
44 -
45 -When you open a file in OnlyOffice:
46 -
47 -1. check if other users are editing the same file. The count appears at the top right corner.
48 -1. perform a trivial edit and save
49 -1. if you are the only user with that file open, you can trust the presence/absence of a warning message from OnlyOffice
50 -1. if multiple users have the file open simultaneously, you can:
51 -11. choose to trust the first user who opened it to have checked, or
52 -11. check in the Drive the timestamp of the file that you just saved
53 -
54 -OnlyOffice will notify you when you try to save a file and the save fails. If that happens:
55 -
56 -1. read the message
57 -1. use File > Download as ... > docx or pptx or xlsx to save the file to your computer
58 -1. close OnlyOffice. (% style="color:#e74c3c" %)**DO NOT KEEP LOCKED FILES OPEN IN ONLYOFFICE.**(%%) It would mislead others.
59 -1. rename the file by adding (% style="color:#3498db" %)//**_UNLOCKED**//(%%) at the end of the filename, before the extension
60 -1. upload the file with its new name
61 -1. work on this new file
62 -
63 -We apologize for the inconvenience and thank you for your understanding.
64 -
65 -The Collaboratory team
19 +