ID — Bahasa Indonesia

Muhamad Irga

Purwokerto, Central Java

Updated

Statistik Siskeudes — Village Finance Analytics in SmartGovt

Village finance dashboards read from Siskeudes and shown inside SmartGovt. My part was the integration: single sign-on, signed iframes, region locking, and safe read access to the production databases for every budget year.

See the service: Village Information Systems

Screenshots

Integration flow from SmartGovt through single sign-on and a signed iframe to Statistik Siskeudes and the per-year Siskeudes databases over an SSH tunnel
Main application view · Open image for full resolution

Overview

What this system does.

Statistik Siskeudes turns the data in Siskeudes, the village finance application, into dashboards: executive and analytic views, cash flow, spending ratios, financial independence, SILPA balances, taxes, payment requests, overdue accountability reports, planning against the village medium-term plan, and compliance checks. The application was built by Ahmad Rizza Fachrudin and Adytia. My work, 12 commits, was bringing it into SmartGovt so village and district officials could use it without a second account.

SmartGovt now opens it through single sign-on: the request carries the user, role, region, destination, expiry, and a one-time nonce, signed with HMAC-SHA256, and the account is provisioned on first use. Pages can also be embedded as an iframe signed over the region code and an expiry time. In embedded mode the app drops its own navbar, sidebar, and login, sizes the page to its content so SmartGovt keeps a single scroll, and redirects to the full sub-path URL so the iframe never falls back to plain HTTP. District and village accounts are locked to their own region in every module, and village names carry their district so identical names stay distinguishable.

On the data side, every Siskeudes budget year can be selected, with one database per year. Reads against the production SQL Server are cached, time-limited, and allowed over the legacy TLS the server still speaks. A small SSH tunnel container forwards several ports at once, such as SQL Server and RDP, and the app is packaged to run in Docker under a sub-path.

Feature inventory

Highlights

16 capabilities verified against the project source.

Finance analytics (team)

  • Executive and analytic dashboards of village finances
  • Cash flow, spending ratios, and financial-independence ratios
  • SILPA balance details, taxes, payment requests, and overdue accountability reports
  • Planning against the RPJMDes, priority programmes, and compliance dashboards

SmartGovt integration (my part)

  • Single sign-on from SmartGovt with HMAC-SHA256, expiry, and a one-time nonce
  • Accounts provisioned on first sign-on with role and region from SmartGovt
  • Signed iframe embedding by region code and expiry time
  • Embedded mode without its own navbar, sidebar, or login
  • Page height that follows content, so SmartGovt keeps one scroll
  • District and village accounts locked to their region in every module
  • Village names suffixed with their district across all menus

Data access and deployment (my part)

  • Every budget year selectable, with one Siskeudes database per year
  • Cached, time-limited reads from production SQL Server over legacy TLS
  • SSH tunnel container that forwards several ports at once
  • Static per-village tokens for embedding on village websites
  • Docker packaging that runs under a sub-path

Tech stack

Built with 7 technologies.

  • Laravel
  • PHP
  • SQL Server
  • HMAC-SHA256
  • Docker
  • Nginx
  • SSH tunnel

Common questions

What people usually ask.

What did you build here?

The integration with SmartGovt and the production data access: single sign-on, signed embedding, region locking, the embedded layout, multi-year databases, safe SQL Server reads, the tunnel, and Docker. The finance modules themselves were written by Ahmad Rizza Fachrudin and Adytia.

Why sign the iframe URL?

The iframe decides which village or district’s finances are shown. Signing the region code together with an expiry time means a copied link stops working and nobody can change the region in the address bar to see another village.

Why are there no screenshots of the dashboards?

They show real village finance data from the production Siskeudes databases. The image here shows the integration flow instead.

Same field

Need something like this?

Send a short brief and I’ll come back with scope, approach, and an honest timeline.