auth-token-manager

JWT tokens for MikoPBX REST API v3 are retrieved by posting credentials to the /auth:login endpoint using curl. This Skill automates that request, stores refresh tokens, and outputs the accessToken to stdout for use in Bearer authentication headers across your API calls.

Yes. This Skill uses curl and bash to automate JWT token acquisition, eliminating manual token requests during API testing and development. It reads credentials from environment variables and outputs tokens directly for chaining in shell scripts.

Set three environment variables: MIKOPBX_API_URL (your API endpoint), MIKOPBX_LOGIN (username), and MIKOPBX_PASSWORD (password). The Skill then handles the token exchange via curl and returns a Bearer token for authenticated REST API requests.

This Skill uses cookie-based refresh tokens and token rotation to maintain seamless authentication sessions. Refresh tokens are stored in a cookie jar, enabling continuous access without re-authentication during API testing workflows.

Yes. The Skill includes an --insecure option to handle self-signed or untrusted HTTPS certificates, useful for development environments where standard certificate validation would block API access.

The Skill provides clear exit codes on success (token retrieved and output to stdout) or failure (invalid credentials, unreachable endpoint, or API errors), allowing shell scripts to branch on authentication outcomes.