In order to enable an iCal export link, your account needs to have an API key created. This key enables other applications to access data from within Indico even when you are neither using nor logged into the Indico system yourself with the link provided. Once created, you can manage your key at any time by going to 'My Profile' and looking under the tab entitled 'HTTP API'. Further information about HTTP API keys can be found in the Indico documentation.
Additionally to having an API key associated with your account, exporting private event information requires the usage of a persistent signature. This enables API URLs which do not expire after a few minutes so while the setting is active, anyone in possession of the link provided can access the information. Due to this, it is extremely important that you keep these links private and for your use only. If you think someone else may have acquired access to a link using this key in the future, you must immediately create a new key pair on the 'My Profile' page under the 'HTTP API' and update the iCalendar links afterwards.
Permanent link for public information only:
Permanent link for all public and protected information:
Puppet 6 tests enabled for hg_ceph and module-ceph. I tried the ai-diff tool on a few machines and seems OK!
Ceph: Projects, News, Other15m
Dan van der Ster
First users are migrated to Dovecot already, so we now need to treat "ceph/kopano" like a production cluster.
Basic tests are being done on the cephfs module.
Configuration modified to use the cephfs mount instead.
Uploaded a file as a test user and can locate it within the mount.
Compiled and run reva client on my local laptop (dev env) and logged in as the same user and listed the file. Download fails for now, might need some config fix because the download uses localhost as url.