auth-token-manager

Получение валидных JWT Bearer токенов для аутентификации MikoPBX REST API v3. Использовать когда нужно тестировать API эндпоинты, отлаживать проблемы аутентификации или при возникновении ошибок 401 Unauthorized. Автоматически обрабатывает вход с username/password и возвращает готовый к использованию access token.

513stars75forksUpdated 2/17/2026

Security #authentication #api-testing #jwt #miko-pbx #token-management #bash-scripts

Security Assessment

Medium Risk(50/100)

Detected risks:

Secret Exposure([README.md] TOKEN=, [README.md] PASSWORD=, [SKILL.md] Token=)

Command Injection([README.md] subprocess.run)

Security Score50/100

About auth-token-manager

The auth-token-manager skill is designed to streamline the process of acquiring valid JWT Bearer tokens for authenticating with the MikoPBX REST API v3. This skill addresses a common challenge faced by developers and testers when working with APIs: acquiring valid authentication tokens. It automates the login process using a username and password, and provides a ready-to-use access token for testing and debugging API endpoints. The skill handles token management, including token validation and expiration checking, making it a valuable tool for efficient API testing and troubleshooting.

FAQ

How do I use this skill to get a valid token?

You can get a valid token by running the provided script `get-auth-token.sh`. Simply ensure that the environment variables for `MIKOPBX_LOGIN` and `MIKOPBX_PASSWORD` are set, and execute the script to receive a fresh access token.

Can I use custom credentials for authentication?

Yes, you can override the default credentials by setting the `MIKOPBX_LOGIN` and `MIKOPBX_PASSWORD` environment variables to your custom values before running the script.

Does this skill support HTTPS with self-signed certificates?

Yes, the skill supports HTTPS with self-signed certificates. Simply set the `MIKOPBX_API_URL` environment variable to the HTTPS endpoint, and the skill will handle the connection.

What happens when the access token expires?

When the access token expires, the skill automatically refreshes it using the refresh token stored in the cookie. The refresh token is valid for 30 days and is rotated on each refresh.

Can I see the full request/response details?

Yes, you can enable debug mode by adding the `--debug` flag when running the `get-auth-token.sh` script. This will display the full details of the request and response.