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:
Meeting with EGI and OSG representatives, and with LHC experiments contact people from IT-ES, to define user requirements and discuss technical issues of common interest related to the Grid Information System.
Present the goals of this meeting and a list of topics to be discussed in future meetings.
Monitoring the BDII
Status and plans to automate sanity checks of the information published by the BDII and the way to trigger notifications to the sites via GGUS.
Understand what it is needed from ginfo and define new requirements if needed.
GLUE 2 plans
Present current GLUE 2 deployment status and gather feedback of what it is missing to be able to start using GLUE 2. Understand experiments needs to have interoperability across the grid infrastructures that are part of WLCG as far as information systems are concerned.