GRegistry — Postman collection
Acest conținut nu este încă disponibil în limba selectată.
API collection for the Registrul Sistemelor Informaționale (RSI).
GRegistry.postman_collection.json— the collection (11 folders, 53 requests). Its built-in variables default to localhost, so it works out of the box against a local backend.GRegistry.server.postman_environment.json— an environment pointing at the deployed server (gregistry.gstack.esempla.systems+ the real Keycloak realminterdictii).
Quick start (localhost)
Section titled “Quick start (localhost)”- Import the collection into Postman.
- Start the backend (
:8085) and Keycloak (:9080, realmjhipster). - Run 00 · Auth → Get Token (password grant) — creds
admin/admin. It stores the access token in the{{token}}collection variable. - Call anything else — every request inherits Bearer
{{token}}automatically. - 01 · Public needs no token.
Server
Section titled “Server”Import GRegistry.server.postman_environment.json and select it. Note: the gregistry-web
client is public / PKCE with Direct Access Grants OFF, so the password-grant token step
will likely fail against the server. Options:
- Use the public (no-auth) endpoints (folder 01) — they work anywhere.
- Or configure the collection’s Authorization → OAuth 2.0 (Authorization Code + PKCE,
auth URL
…/realms/interdictii/protocol/openid-connect/auth, token URL as in the env, clientgregistry-web) and let Postman fetch the token interactively.
/api/v1/public/**— anonymous consultation (ADR-006)./api/**— OIDC bearer (staff/admin)./management/**— ops (health/liveness/readiness/info are public).
09 · Registry Auditis read-only — the audit log is append-only (ADR-003), so there is no create/update/delete.- Enum values are documented in each folder’s description.
- Create requests save the new entity id into a variable (
{{systemId}},{{providerId}}, …) so the get/update/delete/dependency requests chain off it — run Create first.