Skip to content

v0.1.3

Choose a tag to compare

@github-actions github-actions released this 19 Oct 05:25
· 86 commits to main since this release
d3a9055

Fixes from the teams on 0.1.2: positions on org units, the cross-company subject hole in grants,
anchor revoke taking the object's tuples with it, 409 POSITION_HELD with the holder, and the
docs saying plainly that only decisions are revocation-aware; plus the access-token lifetime
from an env var and the documentation site versioned per minor.

  • Assigning a member to a position that already has a holder answers 409 POSITION_HELD with the current assignmentId and memberId in the details; 0.1.2 answered a bare 409 CONFLICT from the database constraint, so the caller could not tell which tenure to end first

  • Docs: only decisions are revocation-aware; a verified token alone serves a disabled user until it expires, so the integrate page, the limitations page and the three SDKs' token-verify docs say to make a decision before serving data

  • Positions can be placed on an org unit: POST /api/org/admin/companies/{id}/positions accepts the orgUnitId the contract already required (under the company, root when absent), and PUT /api/org/admin/positions/{id} retitles or moves a position; 0.1.2 refused orgUnitId with 422 and had no update route, so every position sat on the company root

  • Grants: revoking an object's anchor removes every other tuple on the object in the same transaction, and the owning app can still revoke tuples 0.1.2 left stranded on an unanchored object; 0.1.2 kept those tuples, refused to revoke them, and revived them when the same id was anchored again

  • Security: a grant naming another company's position, group or member as subject is refused with 422, and a check bound to a company ignores such a subject while expanding; in 0.1.2 a tuple viewer @ position:<B position>#holder on company A's object let a user who is a member of both companies reach A's object

  • KIBAN_ACCESS_TOKEN_LIFESPAN sets the realm's access-token lifetime in seconds (default 300); 0.1.2 hard-coded it and bootstrap undid any change made in Keycloak

  • The documentation site is versioned with mike: one folder per minor, latest on the newest minor, dev following main, a version selector in the header; 0.1.2 served one build of main, and the deploy on a tag failed

  • Full changelog: https://github.com/rosschiu/kiban/blob/v0.1.3/CHANGELOG.md

  • Known limitations: https://rosschiu.github.io/kiban/latest/limitations/