- What is jenssegers/mongodb-sentry used for?
- It is a MongoDB-backed user provider for Cartalyst Sentry authentication in Laravel. It stores Sentry users, groups, and permissions in MongoDB collections through jenssegers/mongodb instead of a relational database, while keeping Sentry's familiar authentication and authorization API. It is not the getsentry/Sentry error-monitoring service.
- How do I install jenssegers/mongodb-sentry in a Laravel app?
- Install it with Composer alongside jenssegers/mongodb and Cartalyst Sentry, then register the service provider and configure the collection and model mappings. The only documented release is v1.1.0-beta and it depends on a Sentry feature branch, so you may need dev-stability flags. Pin the exact beta tag, commit composer.lock, and avoid letting minimum-stability dev leak across the root project.
- Does jenssegers/mongodb-sentry work with Laravel 6, 7, 8, 9, 10, or 11?
- No. This package targets Laravel 5.x applications that also use jenssegers/mongodb and Cartalyst Sentry. It has no compatibility matrix for newer Laravel versions and should not be treated as a modernization path. Laravel 5 is end-of-life, so plan a migration off the legacy stack rather than adopting this as a new dependency.
- Is jenssegers/mongodb-sentry the same as Sentry error monitoring?
- No. The Sentry in this package is Cartalyst Sentry, an authentication and authorization library, not the getsentry/Sentry error-tracking service. The name collision is a planning risk because stakeholders may mistakenly scope adoption as observability work. If you need error monitoring, this is the wrong package.
- How do I configure MongoDB collections and connections for Cartalyst Sentry?
- The package provides configurable collection and connection names, so you can point Sentry users, groups, and permission data at the MongoDB database you already run. Review the published configuration for collection and model mappings before wiring it into your auth stack. Confirm group and permission resolution behaves identically to your current provider before switching production traffic.
- Does jenssegers/mongodb-sentry support Sentry users, groups, and permissions?
- Yes. It supports Sentry user, group, and permission persistence through jenssegers/mongodb Eloquent models, so Sentry's full authentication and authorization API remains available with NoSQL storage. The package is a drop-in user provider for MongoDB collections. Validate that your existing group and permission checks return the same results as the relational provider.
- Is jenssegers/mongodb-sentry production ready or still beta?
- The only documented release is v1.1.0-beta, tied to a Cartalyst Sentry feature branch. There is no stable GA release, no compatibility matrix, and no community validation or dependents to rely on. Treat it as evaluation-grade and keep it out of default dependencies unless you are deliberately sustaining a legacy Laravel 5 auth path.
- What are the alternatives to jenssegers/mongodb-sentry for Laravel authentication?
- The higher-value alternative is to move off Cartalyst Sentry altogether and consolidate on native Laravel authentication guards, Sanctum, Passport, or another supported package. Cartalyst Sentry is effectively deprecated and superseded by Sentinel. If you must keep Sentry temporarily, scope this package as legacy maintenance, not as a new adoption.
- How should I test jenssegers/mongodb-sentry before switching authentication traffic?
- Run your full test suite plus focused auth smoke tests for login, group resolution, and permission checks against the MongoDB-backed provider. Compare results with the current relational provider and verify the exact Laravel 5 minor, PHP version, and jenssegers/mongodb version in your fleet. Stage the change and commit the lock file so Composer resolution is reproducible.
- Who maintains jenssegers/mongodb-sentry and is Cartalyst Sentry deprecated?
- Cartalyst Sentry is effectively deprecated and superseded by Sentinel, and upstream maintenance is unlikely. This package is beta-only with no documented stable release, no dependents, and a feature-branch dependency that is not SemVer-governed. Pin the beta tag, vendor or commit-pin the Sentry branch, and plan a funded migration to supported Laravel authentication.