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:
GGUS still holds 178 open tickets for EMI products (22 of them date back
to 2011, 67 were filed in 2012).
With the release of EMI-3 and its first update release the expectation
is that most of the GGUS tickets currently in an open state are solved
now and can be closed.
Therefore, for each open ticket in the support unit(s) you are
responsible for please proceed as follows:
in case a solution has been released with EMI-3, close the ticket as solved
in case a solution will be implemented with the final EMI-3 update
release, comment this in the ticket
in case a solution will not be implemented at all, close the ticket
in case a solution will be implemented in your product after the end
of EMI, state this in the ticket with a realistic date, when it will
be fixed (ETA)