summaryrefslogtreecommitdiff
path: root/db
AgeCommit message (Collapse)AuthorFilesLines
7 hoursfeat: auto-refresh expired tokens before /article and /tokenHEADmasterwikiapiserver1-4/+61
- EnsureValidToken checks access_token_created age before each request. If token is >24h old, refreshes via WikimediaTokenRefresh (or falls back to full re-auth via WikimediaLogin). - Register now upserts: updates tokens for existing users instead of failing with 'username already exists'. - Both /article and /token call EnsureValidToken before responding.
39 hoursfeat: log article API failures to databasewikiapiserver1-0/+24
- Created api_logs table (username, article_name, status_code, response_time_ms, error, request_url) - GetArticle logs failures (network errors and non-2xx responses) with timing, status code, and response body - Successful requests are not logged
45 hoursfeat: GET /token?username=... returns access_token and valid_untilwikiapiserver1-0/+5
Returns the stored access_token and the timestamp when it was created (access_token_created). Returns 401 for unknown users.
46 hoursfeat: token refresh with age-based logicwikiapiserver1-62/+129
- RefreshTokens checks token age and chooses the right path: - refresh_token > 90 days: re-auth via WikimediaLogin (full login) - access_token > 24 hours: refresh via WikimediaTokenRefresh - otherwise: return current tokens - WikimediaTokenRefresh posts to /v1/token-refresh endpoint - Login also uses WikimediaLogin instead of local RotateTokens - Removed dead RotateTokens, RefreshByToken, and randomHex - DSN includes parseTime=true for timestamp columns
46 hoursrefactor: extract Wikimedia auth into reusable functionwikiapiserver1-10/+17
- WikimediaLogin is a standalone function: POSTs to auth.enterprise.wikimedia.com and returns the tokens. Can be called from any flow. - Register composes WikimediaLogin + CreateAccount - CreateAccount now takes tokens as arguments (pure DB insert)
47 hoursfix: update queries for new refresh_token_created column and add error loggingwikiapiserver1-3/+3
- INSERT and UPDATE now set both refresh_token_created and access_token_created timestamps - Register handler logs the actual error on failure
48 hoursrefactor: store tokens in plaintextwikiapiserver1-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.
48 hoursfeat: integrate Wikimedia Enterprise auth API on registerwikiapiserver1-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.
48 hoursrefactor: remove token generation from registerwikiapiserver1-15/+7
Register only saves username and plaintext password. Token fields are left empty until set by the Wikimedia API.
48 hoursrefactor: store password in plaintextwikiapiserver1-6/+6
Remove SHA-256 hashing for the password column. Tokens still hashed with SHA-256 in the database.
48 hoursfeat: initial wiki API server with account managementwikiapiserver1-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)