feat: deprecate ISSUER_DID and ISSUER_FRAGMENT

.env.example

@@ -14,5 +14,3 @@ UNICORE__LEDGER_SPONSORING_SERVICE__ACCESS_KEY="<your-access-key"
 # Uncomment to enable DID IOTA for testing purposes
 # UNICORE__SECRET_MANAGER__STRONGHOLD_PATH="agent_secret_manager/tests/res/test.stronghold"
 # UNICORE__SECRET_MANAGER__ISSUER_EDDSA_KEY_ID="9O66nzWqYYy1LmmiOudOlh2SMIaUWoTS"
-# UNICORE__SECRET_MANAGER__ISSUER_DID="did:iota:rms:0x42ad588322e58b3c07aa39e4948d021ee17ecb5747915e9e1f35f028d7ecaf90"
-# UNICORE__SECRET_MANAGER__ISSUER_FRAGMENT="bQKQRzaop7CgEvqVq8UlgLGsdF-R-hnLFkKFZqW2VN0"

agent_application/CONFIGURATION.md

@@ -40,8 +40,6 @@ All environment variables need to be prefixed with `UNICORE__` to prevent confli
 | `UNICORE__SECRET_MANAGER__STRONGHOLD_PASSWORD` | The password to unlock the stronghold.            | -             | -                             |
 | `UNICORE__SECRET_MANAGER__ISSUER_EDDSA_KEY_ID` | The key ID of the EDDSA (Ed25519) key to be used. | -             | -                             |
 | `UNICORE__SECRET_MANAGER__ISSUER_ES256_KEY_ID` | The key ID of the ES256 key to be used.           | -             | -                             |
-| `UNICORE__SECRET_MANAGER__ISSUER_DID`          | The DID of the issuer.                            | -             | -                             |
-| `UNICORE__SECRET_MANAGER__ISSUER_FRAGMENT`     | The fragment to be used.                          | -             | -                             |
 
 ## Look and Feel
 

agent_application/docker/README.md

@@ -39,17 +39,6 @@ docker compose up
 > [!NOTE]
 > In case you need a base bath (for example when running behind a reverse proxy), you can set the `UNICORE__BASE_PATH` to a value such as `ssi-agent`.
 
-## IOTA DIDs
-
-By default, UniCore uses the JWK DID Method to generate and manage DIDs. However, UniCore also supports the IOTA DID
-Method, which leverages the IOTA Tangle to store your DID document. To enable the IOTA DID Method, set these environment
-variables:
-
-```yaml
-UNICORE__SECRET_MANAGER__ISSUER_DID: <your-pre-existing-IOTA-DID>
-UNICORE__SECRET_MANAGER__ISSUER_FRAGMENT: <your-pre-existing-IOTA-DID-fragment>
-```
-
 ## Leveraging Just-in-Time Data Request Events
 
 UniCore facilitates dynamic integration with external systems through just-in-time data request events, dispatched seamlessly via an HTTP Event Publisher. This enables real-time data retrieval and on-demand generation, enhancing flexibility and efficiency in your SSI ecosystem.

agent_application/docker/compose.yaml

@@ -43,8 +43,6 @@ services:
 
       # Uncomment the following lines to use the DID method `did:iota:rms`
       # UNICORE__SECRET_MANAGER__ISSUER_KEY_ID: "9O66nzWqYYy1LmmiOudOlh2SMIaUWoTS"
-      # UNICORE__SECRET_MANAGER__ISSUER_DID: "did:iota:rms:0x42ad588322e58b3c07aa39e4948d021ee17ecb5747915e9e1f35f028d7ecaf90"
-      # UNICORE__SECRET_MANAGER__ISSUER_FRAGMENT: "bQKQRzaop7CgEvqVq8UlgLGsdF-R-hnLFkKFZqW2VN0"
     volumes:
       - ../../agent_application/config.yaml:/app/agent_application/config.yaml
       # - ../../agent_secret_manager/tests/res/test.stronghold:/app/res/stronghold

agent_shared/tests/test-config.yaml

@@ -62,5 +62,3 @@ secret_manager:
   stronghold_path: "../agent_secret_manager/tests/res/selv.stronghold"
   stronghold_password: "VNvRtH4tKyWwvJDpL6Vuc2aoLiKAecGQ"
   issuer_eddsa_key_id: "UVDxWhG2rB39FkaR7I27mHeUNrGtUgcr"
-  issuer_did: "did:iota:rms:0x42ad588322e58b3c07aa39e4948d021ee17ecb5747915e9e1f35f028d7ecaf90"
-  issuer_fragment: "bQKQRzaop7CgEvqVq8UlgLGsdF-R-hnLFkKFZqW2VN0"