- How do I install kristories/novassport in a Laravel Nova app?
- Install it with composer require kristories/novassport, then register the tool in your NovaServiceProvider tools() method. Confirm that Laravel Passport is installed and that the oauth_clients and oauth_access_tokens migrations exist. Because the last release is from January 2022, expect dependency conflicts on a current Laravel or Nova stack and treat installation as a spike rather than a plan.
- Does kristories/novassport work with Laravel 11 or 12?
- The last release is January 2022, which predates Laravel 10, 11, and 12, so official support is unlikely. Composer constraints will probably conflict with a current stack and may require a fork or a --with-dependencies fight. Validate install and core flows in a branch before committing to it.
- Is Nova Passport compatible with Laravel Nova 5?
- It is not guaranteed. The package predates Nova 5, and Nova is a closed-distribution package with its own major cadence. Assume you will need to fork and update the Nova tool class and asset compilation for Nova 5.
- Can I view an existing Passport client secret after creating it?
- Generally no, not with modern Passport. Passport 11 moved to hashed client secrets, so the plaintext secret is not recoverable after creation. Any UI that displays or re-copies an existing secret is structurally broken regardless of whether the package installs. Only rely on secret display at the create step.
- Do I need this package if my API uses Sanctum instead of Passport?
- No. This package is a Nova presentation layer over Passport's OAuth tables, so it has no surface area if you authenticate APIs with Sanctum. Sanctum is Laravel's guidance for new projects, while Passport is for genuine OAuth2 server requirements such as third-party clients, authorization-code flows, and scopes.
- What are the alternatives to kristories/novassport?
- For most teams the better option is roughly 200 lines of in-house Nova tooling over the oauth_clients and oauth_access_tokens tables, or the artisan passport:client command for client creation. If you need the existing UI now, fork and vendor the repository into your org and pin it to your Laravel, Nova, and Passport versions.
- Is it safe to manage OAuth clients and tokens inside Laravel Nova?
- It inherits Nova's authorization, but this is a high-blast-radius view of credential material. Add an explicit gate or policy on the tool, enable audit logging, and verify secrets are never written to logs or serialized into Nova responses beyond the create step. There is no upstream CVE monitoring or security advisory path, so you own that risk.
- Is kristories/novassport still maintained?
- No active maintenance is evident. There have been no releases since January 2022 and there is no maintainer SLA, CVE monitoring, or security advisory process. For a component that touches OAuth credentials, treat it as unmaintained and fork it if you decide to keep it.
- How do I revoke OAuth clients and access tokens with this tool?
- The tool provides UI actions to revoke clients and tokens against Passport's tables. Because a mis-clicked revoke can break integrations, treat the console as internal-operator-only and gate it behind an explicit Nova permission. Confirm the blast radius and test revocation in staging before exposing it to tenant-facing admins.
- How should I evaluate or test kristories/novassport before adopting it?
- Run a short research spike: install in a throwaway branch on your real Laravel and Nova versions, resolve Composer constraints, and exercise create, edit, revoke, and secret-display flows. Check whether your Passport version hashes secrets and whether the UI still behaves. Decide between forking and an in-house replacement before adding it as a dependency.