Log

 

e-ID in Uri

Kann die neue Swiss e-ID die Privatsphäre der Nutzern online und offline schützten?

Digital Cluster Uri

Team Readme
✨ Demo
↓  Open

e-ID und Privatsphäre

Kann ich mich mit e-ID online authentifizieren ohne meine Privatspäre zu bedrohen

Was ist e-ID?

  • Die e-ID ist die digitale Form des Ausweises
  • Die Nutzung ist ein freiwilliges und kostenloses Zusatzangebot
  • Kann online und offline benutzt werden
  • e-ID und Swiyu sind nun in Public Beta

Warum Privatsphäre?

  • Immer mehr persönlichen Daten landen in Datenlecks
  • Überregulierung vom Internet verschlimmert das Risiko
  • e-ID verspricht Datensparsamkeit und Unverknüpfbarkeit

Erwartungen

  • In meiner Swiyu-App ein digitales Zeugnis über meine Teilnahme an den Hackdays Uri erhalten
  • Eine Webseite, wo ich mich mit Swiyu authentifizieren kann und meine Teilnahme an den Hackdays beweisen
  • Meine persönliche Daten muss ich dabei nicht preisgeben

Outlook

  • Digitale Mitgliedschaft beim Digital Cluster Uri
  • Sichere Online-Dienste für Urner

Ressourcen und Hilfsmittel

Challenge Owner

Swiyu Demo for Hackdays Uri 2026

An attempt to setup Swiyu infrastructure to be able to issue and verify custom credentials compatible with Swiss e-ID.

0. Prerequisites

This repo requires Direnv and Devenv for reproducible development setup. Swiyu demo issuer and didtoolbox are part of this repo as Git submodules. Make sure to run git submodule update --init first. Docker and Docker Compose are required to run the infrastructure.

1. Onboarding

Swiyu ecosystem requires issuers to be onboarded and approved before they can participate in credential issuance.

Follow onboarding guide and prepare .env file (not part of this repo) with values from onboarding process. See example.env for required variables.

2. Setup

  1. Create DID by running create-did.
  2. Extract $IDENTIFIER_REGISTRY_ID and $IDENTIFIER_REGISTRY_URL into .env.
  3. Build didtoolbox by running build-didtoolbox.
  4. Run upload-did-log.
  5. Verify DID log by running get-did-log.
  6. Build demo issuer by running build-issuer.
  7. Update your /etc/hosts to resolve issuer.digital-cluster-uri.ch as 127.0.0.1.
  8. Run issuer-compose up -d to start issuer and its dependencies.

Now issuer should run. Unfortunately at this stage the next step of the guide failed with an error ch.admin.bj.swiyu.issuer.common.exception.ConfigurationException: Failed to sign status list JWT with the provided key.

I probably misconfigured something and mixed some parameters. To be honest, the whole experience was way too complicated and confusing: During manual onboarding process I created 9 secret values and subscribed for 4 different APIs, various keys and parameters and all named confusingly similar. On top of that, onboarding requires sending an email for approval. Since I did this process on Friday afternoon during Hackdays Uri, I never received a reply during the hackathon challenge :(

License

This code is dedicated to Public Domain and distributed under conditions of Unlicense.

Preview of external content.
👋 E-mail ✨ Demo 💻 Source
All attendees, sponsors, partners, volunteers and staff at our hackathon are required to agree with the Hack Code of Conduct. Organisers will enforce this code throughout the event. We expect cooperation from all participants to ensure a safe environment for everybody.

The contents of this website, unless otherwise stated, are licensed under a Creative Commons Attribution 4.0 International License. The application that powers this site is available under the MIT license.


Previous
Hackdays Uri 2026
Next project