Simulates the client's ERP backend for the VesselMan hot-link flow (Custom Token Exchange). Click a hot-link as if you were that ERP user.
| ERP user | Vessel user | Auth0 user_id | Actions |
|---|---|---|---|
erp_user_1 | havard@vesselman.com |
auth0|69dcf6a2978ffff6332f75f0 |
Hot-link Debug Dry-run |
erp_user_2 | havard@vesselman.com |
auth0|69dcf6a2978ffff6332f75f0 |
Hot-link Debug Dry-run |
erp_user_3 | operations@northagency.no |
auth0|6a21582266777b8516430bc2 |
Hot-link Debug Dry-run |
erp_user_4 | operations@northagency.no |
auth0|6a21582266777b8516430bc2 |
Hot-link Debug Dry-run |
erp_user_5 | h.jorstad@marcura.com |
oidc|entra-oidc-marcura-dev|YFqi0hZc-VD0LmiaZcZiSyNS6xC9UVBIYFbnDfQO258 |
Hot-link Debug Dry-run |
mode : redirect issuer (iss) : https://erp-dev.vesselman.com audience (aud) : urn:vesselman:token-exchange subject_token_type : urn:vesselman:erp-assertion auth0 domain : marcura-dev.eu.auth0.com bff client_id : 6c9663GC8oDdv7qVUfNyLZ8k3Nd50laI bff private key : /opt/erp/keys/vesselman_bff_private.pem vesselman redirect : https://dev.vesselman.com jwks : https://erp-dev.vesselman.com/.well-known/jwks.json
⚠ For a live exchange, the Auth0 Action secrets ERP_JWKS_URI /
ERP_ISSUER must point at this server via a publicly reachable URL
(tunnel for localhost), and the vessel-users must exist in Auth0 with their real
auth0|… ids in vessel-users.json.