EPFL/SPC External Collaborator Access Migration

This page provides instructions for external collaborators of the Swiss Plasma Center (SPC), regarding the mandatory migration to the new EPFL authentication system.

Overview

  • The EPFL legacy guest account system and "Tequila authentication" are being decommissioned.
  • To maintain access to SPCwiki, all external users must be accredited in EPFL as external collaborators.
  • LAC accounts to connect to computing resources are separate and unaffected at this point.

During this process, the new access rights form has to be signed.

  • 31 March 2026: End of Life for Tequila authentication.
  • 15 March 2026: Deadline to send the form to keep access on 31 March 2026.
  • If you do not need immediate access, please wait until you do, to help us allocate resources effectively during this migration.

Migration Procedure

  • If you do not wish to keep your access, no action is needed. Your access will be removed once expired.
  • To explicitly ask your access to be revoked, fill the Question/Support form and select "I want to keep my access to SPCWiki" -> NO
  • Otherwise complete the following steps at least 2 weeks before you need access to SPCWiki (If you want to keep access on March 31st, do it by March 15, 2026)

1. Identify your SPC Contact

Your "Main Contact Person" is typically the SPC staff member you collaborate on your research project and who initially requested your access. If you collaborate with multiple people, choose the one most closely related to your primary activity.

2. Submit the Data Access Form and identity document

  • Download the New Data Access Form (PDF/Docx) (See below for Access Roles)
  • Email the completed document to your contact person at SPC.
  • Send a copy of your valid identity document to edith.grueter@epfl.ch

3. Account Activation and 2FA

Once processed, you will receive an automated email from EPFL IT with instructions

Access roles

  • During migration to the new authentication system, data will be collected on finer grained access rights on computing resources.
  • Initially, this won't change your workflow with computing resources such as LAC.
  • Access rights for computing resources are in development and you'll receive further communications.
  • If unsure, only select "Documentation" and "Read access", further access can be demanded later.

Access types:

  • Documentation (SPC wiki): Default rights to access SPCWiki. Must be selected if user wants to keep their SPCWiki access.
  • Read access to TCV data: Users with this right have access to log in to certain resources that have read-only access to TCV data and software.
  • Write access to TCV analysis results: Users with this right have access to log in to certain LACs, Some collaborators may have access to write results tree or run certain codes to generate analysis results.
  • TCV Private Network (For diagnostics control etc.): Users with this right have access to log in to hosts that have access to TCV private network. This is ONLY granted if the user requires to run/manage a diagnostic in TCV, or similar reasons.
  • Access to Falcon system and network: Access given to collaborators of Falcon project.
  • Other access: Comment and justify. This is for collaboration for other projects such as: Defuse Project, Digital Twin Project.

Frequently Asked Questions

Can I ask for additional access later

Yes, if you are unsure about access requests on computing resources, demand the minimum for now. You can ask for further access later.

What happens if I miss the March 31st deadline?

  • Your wiki contributions will remain.
  • You will just not be able to log-in to SPCWiki before you complete the procedure.
  • You are NOT going to lose access to LAC resources.
  • You can do the procedure in the future, at least 2 weeks in advance.

What happens to my SPC LAC account

  • Initially LAC account will not be affected
  • In few months, you'll receive further communications, and LAC account will be deactivated if you haven't migrated your guest account to EPFL account.

Support and Updates

  • For any issues observed during this migration, please keep checking this page, which will be kept up to date.
  • If your question is unanswered, fill the Question/Support form
  • We may not answer each question/request separately, but we will answer common questions on this page.