- What is NovaPassport used for in a Laravel app?
- NovaPassport is a Laravel Nova tool that provides an admin interface for Laravel Passport OAuth clients and access tokens. It lets administrators create, view, and revoke API credentials from Nova instead of building custom Passport screens. It is best suited to applications already using both Laravel Nova and Laravel Passport.
- How do I install wearedevtical/novassport in Laravel Nova?
- Install it with Composer using wearedevtical/novassport, then register the Nova tool and publish or review its config as documented. Confirm whether the package relies on existing Passport tables or publishes its own migrations. Start in staging with a pinned ^2.0.2 constraint and inspect the v2.0.2 diff before promoting to production.
- Which Laravel, Nova, Passport, and PHP versions are supported by NovaPassport?
- The provided context does not list an exact compatibility matrix, so verify the package README and Composer constraints before rollout. Check Laravel major and minor versions, Nova major version, Passport major version, PHP version, and frontend asset build expectations. Nova major upgrades are the most likely compatibility breakpoint for a Nova tool.
- Does NovaPassport replace Laravel Passport?
- No. NovaPassport is an admin UI and integration layer for Laravel Passport, not a standalone OAuth2 server or a replacement for Passport. It surfaces Passport client and token administration inside Nova. Your application still needs Laravel Passport installed and configured.
- How do I configure NovaPassport after installation?
- Publish and review the package config, register the tool in Nova, and verify config keys, namespace, and published asset paths after the rebrand. Confirm whether the package expects existing Passport migrations or ships its own. Keep the config in version control and validate it in staging before production.
- Can NovaPassport safely manage OAuth client secrets and token revocation?
- NovaPassport exposes client and token management screens, but the provided context does not confirm how Nova authorization policies are enforced. Restrict access to a limited admin group and review Nova gates or policies around client secrets, token issuance, and revocation. Test secret visibility and revocation behavior in staging before relying on it in production.
- How should I test NovaPassport before using it in production?
- Run it in staging with a pinned version and inventory existing Passport clients and tokens first. Test OAuth client creation, secret visibility, token issuance, revocation, and Nova authorization boundaries. Compare the v2.0.1 to v2.0.2 diff for rebrand, namespace, config, and asset changes before rollout.
- What changed in NovaPassport 2.0.2 and is it a breaking upgrade?
- The v2.0.2 release notes list Remove Empty CSS, Sync and Refactoring, and Rebrand changes. Semver does not signal a breaking change, but the rebrand and refactor warrant a diff review for package identity, namespaces, config keys, and asset paths. The context does not detail a specific upgrade path from 2.0.1 or 1.x, so test in staging and plan Composer aliases or replacements if the package name changed.
- Are there alternatives to NovaPassport for managing Passport in Laravel?
- If your application already uses Laravel Nova and Passport, NovaPassport is a focused admin UI option. If you do not use Nova, native Passport tooling or a custom admin screen is usually a better cost-benefit choice. Do not adopt Nova solely to use this package.
- How is NovaPassport maintained and what are the production risks?
- NovaPassport appears small and community maintained through GitHub issues and pull requests, with no commercial SLA indicated. Pin versions and treat Nova and Passport upgrades as planned maintenance events. Assign explicit internal ownership and monitor token-management activity because dependency coupling is the main production risk.