Download the PHP package nawasara/registry without Composer

Nawasara Registry

Master data for the Nawasara superapp framework: organizational units (OPD), persons in charge (PIC), and a generic asset ownership index that other packages link into.

Features

• OPD: code, name, address, phone, email, plus parent_id for institutions that sit under another OPD
• Unit: divisions inside an OPD ("BIDANG APLIKASI DAN INFORMATIKA")
• Employee: employment data per user, sourced from SIMAS Hebat
• Membership: which user belongs to which OPD, the relation other packages scope against
• Asset: a generic ownership record keyed by (package_ref, external_id). Other packages (Cloudflare DNS, WHM Account, Email account) write here with their canonical IDs so the dashboard can render an "OPD / PIC" column on every resource list and a single OPD detail page can show every asset they own
• Activity log: every write is captured via spatie/laravel-activitylog
• Admin pages: Livewire CRUD for OPD, Membership, and Asset with search, filter, and detail modals

Appointing a PIC: why it calls an external system

Appointing someone is not a field write here. It goes through PicAssignmentService, which first asks SIMAS Hebat where that person currently works.

The reason is that nothing tells Nawasara about a transfer. A membership is recorded once and then sits there forever. Somebody who moved from Kominfo to Dinas Pendidikan last month still carries Kominfo's opd_id, and since ScopedToOpd filters rows by exactly that column, appointing them to a new asset would hand them an OPD's data they no longer belong to. That is a leak, not a stale label.

So one assignment does three things:

1. refreshes the person's employment data (nama_jabatan, jenis_jabatan, jenis_kepegawaian, simas_unit_kerja)
2. creates the OPD and sub-unit when the registry does not have them yet
3. records the membership and writes the asset

Three decisions in there are easy to reverse without knowing why they were made:

A mismatch is held, never resolved automatically. When SIMAS places someone elsewhere, PicMismatchException is thrown and the screen shows both sides. Overwriting opd_id would revoke someone's access with nobody told, and if the prefix matcher is what slipped, the access revoked is the correct one.

It throws rather than returning a value. A return value can be ignored without consequence; what hangs on this one is who may read an OPD's data.

An OPD cannot be created without a SIMAS reply, and the reply is stored in the audit entry. An OPD is a permission container. One born from an admin's memory, with only "admin X created OPD Y" recorded, cannot be judged right or wrong by anyone six months later.

When SIMAS is unreachable, assigning to an OPD that already exists still goes through on previously verified data, with simas_synced_at left untouched and the audit entry marked unverified. Creating a new OPD does not: without a reply there is no basis for it.

unit_kerja is matched by prefix, not split

SIMAS returns <OPD NAME><space><SUB-UNIT> with no separator, and OPD names themselves contain commas and the word "DAN":

Splitting that on a comma, or hunting for the word "BIDANG", is wrong on some rows. UnitKerjaMatcher asks the opposite question instead: does this text start with an OPD we already know? The longest matching prefix wins and the remainder is the sub-unit.

An unrecognised prefix returns nothing rather than the nearest guess. SEKRETARIAT DAERAH is genuinely missing from the registry, and a near-miss there would give someone another OPD's data.

NIP is read-only on that screen

The NIP links a person to their Keycloak account, where the username is the NIP on all 10,430 production users. A mistyped digit cuts an account loose from its owner, and nip is unique, so pasting someone else's turns into an error rather than two accounts sharing an identity. A NIP that is genuinely wrong is fixed at the source. Keycloak is never written to from here either, though the Admin API would allow it.

Schools are OPDs with a parent, bidang are units

BIDANG APLIKASI DAN INFORMATIKA and SD NEGERI 1 TEGALREJO arrive in the same position of unit_kerja but are not the same kind of thing. A bidang is a division inside an OPD; a school is its own institution under one, with its own assets, PIC and budget.

Schools therefore become OPD rows with parent_id, which is what keeps a teacher scoped to their own school instead of to all of Dinas Pendidikan.

⚠️ parent_id records the relationship only. ScopedToOpd still matches one opd_id exactly, so a parent does not see its children's data. Widening that would change data isolation in hibah, aspirations and nawasara-api at once, and it is its own decision rather than a side effect of adding a column.

The shared picker

Four packages carried their own pjCandidates(), identical apart from whitespace. <livewire:nawasara-registry.pic-picker> replaces them and reports the choice over an event, so each host keeps its own property names:

The picker writes nothing; the host still saves through PicAssignmentService. A check living in Blade would be reached around by seeders, sync jobs and any package that never heard of the rule.

Status: registry uses it. cloudflare, whm and zoom still have their own copies and keep working; they move one at a time, each with its own tag.

Installation

Auto-discovered.

Register the package with Tailwind, in resources/css/app.css:

Without it none of the package's Tailwind classes compile, and the pages render unstyled rather than erroring.

SIMAS Hebat credentials

Fill the simas-hebat group in the Vault panel (base_url, token, app_id). Until that is done, the OPD and PIC selects still work; only the NIP lookup is unavailable, and it says so on screen rather than failing silently.

Set SIMAS_TEST_NIP to any real NIP if you want the Vault "Test" button to verify the connection.

⚠️ Do not hardcode these. They appear in plain text inside SimasHebatAuthenticator.java because a Keycloak authenticator cannot read Vault; that is a constraint of where it runs, not a pattern to copy.

⚠️ The source firewall blocks the calling IP after a handful of requests, and the block is total: NIPs that worked a moment ago start returning 403, including the docs page. That is why the client never retries and why the lookup is a button rather than a live-bound field.

Asset linking pattern

Other packages create an asset row whenever they create a managed resource:

⚠️ Note what is not in that payload: pj_user_id. Appointing someone runs through PicAssignmentService (see above), not through a field write, because it re-checks their posting and may create an OPD:

Resource list pages then look up the asset map in one query:

Pages

API

Requires nawasara/api. If that package is not installed, the routes are not mounted.

Registry is the organization's master data, so these are the most useful endpoints for sharing data between applications: two systems can use the same OPD list instead of each keeping a copy that slowly drifts apart.

Scope

Membership is separate because it maps people to organizations, while the other two are organization data.

Endpoints

Multi-value parameters accept commas: ?type=domain,subdomain.

Use an OPD's code and a person's keycloak_id to link data across systems; both survive a change of name or username. A row's id only means something inside Nawasara.

What is not returned

• Asset notes: free-form operator notes. Since there is no rule about what may be written there, there is no guarantee the content is safe to expose.
• ticket_ref, external_id: internal references and ids in third-party systems; only useful to someone with access to those systems.
• The local user_id on memberships; keycloak_id is returned instead.

Note if ScopedToOpd is applied to Asset

Right now Asset does not use that trait. If it is ever applied, the asset endpoints must be reviewed: MembershipResolver treats a request with no logged-in user as privileged, and an API token has no user, so per-OPD filtering would be skipped silently with no error.

Author

Pringgo J. Saputro <[email protected]>

License

MIT