wikimedia-auth-oauth

To authenticate a bot for editing Wikipedia pages, you can use OAuth 1.0a/2.0 flows or create bot passwords. This involves registering an OAuth consumer, managing tokens, and securely storing credentials to ensure compliant API access.

Managing CSRF tokens for Wikimedia API editing requires requesting tokens through authenticated sessions before performing write actions. This skill handles CSRF token management automatically to ensure secure editing and prevent cross-site request forgery.

Use bot passwords instead of OAuth for personal bots, cron jobs, and single-user scripts where full OAuth consumer registration is unnecessary. Bot passwords provide simpler credential management for individual automated tasks on Wikimedia APIs.

Yes, Wikimedia API authentication supports both OAuth 1.0a and 2.0 flows. This includes consumer registration, token management, and permission checks to ensure secure access for editing, patrolling, and uploading operations.

Securely storing API credentials and bot passwords requires following best practices for credential management. This skill implements secure storage practices to protect OAuth tokens and bot passwords used by Wikimedia API clients.

Wikimedia bots fail permission checks during API editing when OAuth scopes or bot account rights are insufficient. This skill implements permission checks for bot accounts and OAuth users to ensure compliance with editing policies.