Download the PHP package sharadkashyap/php-api-authentication-debugger without Composer
On this page you can find all versions of the php package sharadkashyap/php-api-authentication-debugger. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download sharadkashyap/php-api-authentication-debugger
More information about sharadkashyap/php-api-authentication-debugger
Files in sharadkashyap/php-api-authentication-debugger
Package php-api-authentication-debugger
Short Description A framework-independent PHP tool for diagnosing API authentication failures.
License MIT
Informations about the package php-api-authentication-debugger
PHP API Authentication Debugger
A framework-independent PHP CLI tool that turns API authentication failures into clear findings and safe, actionable recommendations.
It helps diagnose common 401 Unauthorized and 403 Forbidden responses without exposing credentials in diagnostic output.
Client presentation
Download editable PowerPoint
What it diagnoses
- Missing, empty, malformed, expired, or revoked Bearer tokens
- Missing or invalid API keys
- Basic authentication formatting and credential issues
- Custom authentication-header problems
- Conflicting authentication mechanisms in one request
- HTTP
401and403failures - Common permission, scope, role, network, and policy causes
Security first
Credentials are sanitized before they appear in diagnostic results. Use only fake, redacted, or safely sourced values when running diagnostics. Never commit real tokens, API keys, passwords, or production request captures.
Requirements
- PHP 8.2 or later
- Composer
Installation
Quick start
Diagnose a 401 response where no credentials were attached:
Example output:
Usage
| Option | Description |
|---|---|
--method=<method> |
HTTP method; defaults to GET |
--status=<code> |
HTTP response status code |
--header="Name: Value" |
Request header; may be repeated |
--help |
Show usage information |
Bearer token example
API-key example
The output is JSON, making it suitable for local troubleshooting, scripts, CI logs, or a future web interface.
Exit codes
| Code | Meaning |
|---|---|
0 |
The request has no diagnostic failure |
1 |
Invalid command input or an application error |
2 |
A diagnostic failure was found |
Development checks
Project status
The core diagnostic engine and CLI are complete. Current work focuses on documentation, CI automation, and portfolio-ready release polish.
License
This project is licensed under the MIT License.