wikiapiserver - Small server utility to make working with wikimedia enterprise api a little bit easier.

Age	Commit message (Collapse)	Author	Files	Lines
41 hours	fix: update queries for new refresh_token_created column and add error logging	wikiapiserver	1	-3/+3
	- INSERT and UPDATE now set both refresh_token_created and access_token_created timestamps - Register handler logs the actual error on failure
42 hours	refactor: store tokens in plaintext	wikiapiserver	1	-10/+4
	Remove SHA-256 hashing of refresh_token and access_token. Tokens are now stored and looked up as-is, matching the Wikimedia API format.
42 hours	feat: integrate Wikimedia Enterprise auth API on register	wikiapiserver	1	-6/+58
	Register now calls POST /v1/login on the Wikimedia auth endpoint to obtain refresh_token and access_token. Tokens are hashed (SHA-256) before storage. If the API call fails, registration fails.
42 hours	refactor: remove token generation from register	wikiapiserver	1	-15/+7
	Register only saves username and plaintext password. Token fields are left empty until set by the Wikimedia API.
42 hours	refactor: store password in plaintext	wikiapiserver	1	-6/+6
	Remove SHA-256 hashing for the password column. Tokens still hashed with SHA-256 in the database.
42 hours	feat: initial wiki API server with account management	wikiapiserver	1	-0/+210
	- HTTP API with JSON over configurable port (default 8080) - Endpoints: POST /register, POST /login, POST /refresh, GET /health - MariaDB storage with SHA-256 hashed credentials and tokens - Token rotation on login and refresh - Config loaded from config.json (not tracked in git) - Graceful shutdown on SIGINT/SIGTERM - Connection pool (25 max open, 10 idle, 5min max lifetime)