iSHARE Token Creator (test environment)

Use this tool to test the full DSGO AuthZ flow. It performs three steps:

  1. Authenticate — builds a JWT client_assertion signed with your private key and certificate, then exchanges it for a Bearer token at POST /token.
    The server verifies the JWT signature against the x5c certificate, checks that the organizationIdentifier matches the JWT subject, and validates the caller against the Digigo participant registry.
  2. Health check — calls GET /api/health with the Bearer token to verify the token is accepted by the API.
  3. Authorization evaluation — sends a demo evaluation request to POST /api/evaluation through the Casbin authorization engine.
    Uses the same identities as the authentication: the test client (did:ishare:EU.NL.NTRNL-99999998) asks to read /products at the server (did:ishare:EU.NL.NTRNL-99999999). Both are registered participants in Digigo.
Demo scenario: "May test client (did:ishare:EU.NL.NTRNL-99999998) read /products at server (did:ishare:EU.NL.NTRNL-99999999)?"
Ensure demo policies are present: php bin/console doctrine:migrations:migrate

Values entered here are not stored.

Step 1 — Authentication

No token response yet. Submit the form above.

Step 2 — Health check (Bearer token verification)

No health response yet.

Step 3 — Authorization evaluation (Casbin)

Request sent to POST /api/evaluation:

{
    "subject": {
        "type": "service-consumer",
        "id": "did:ishare:EU.NL.NTRNL-99999998"
    },
    "resource": {
        "type": "api",
        "id": "\/products",
        "properties": {
            "service_provider": "did:ishare:EU.NL.NTRNL-99999999"
        }
    },
    "action": {
        "name": "can_read",
        "properties": {
            "method": "GET",
            "license": "DSGO.0001"
        }
    }
}

No evaluation result yet.