Skip to content
This repository was archived by the owner on Jan 1, 2026. It is now read-only.
This repository was archived by the owner on Jan 1, 2026. It is now read-only.

Some checks don't work in a multitenancy app #40

Description

@RobertCordes

Versions

  • PHP version: 7.4.12
  • Laravel version: 8.25.0
  • Enlightn version: 1.9.0 OSS

Description

Hi, I'm trying to run Enlightn in a multitenancy setup. I'm using the laravel-multitenancy package from Spatie. Some checks just don't seem to work with this kind of setup.

Steps to Reproduce

Nothing special. Just set up a Laravel app with the multitenancy package as per documentation.

Expected behavior:
For all the checks to work I guess 😇 Although I don't really expect this to work out of the box. For example Invoker has a feature where you can define some preload code. So the expected behavior would probably be some way to configure this.

Actual behavior:
When I run Enlightn some checks just throw an exception with Target class [currentTenant] does not exist. In the OSS version of Enlightn the following checks don't work:

  • Session Driver Analyzer
  • CSRF Analyzer
  • Encrypted Cookies Analyzer
  • HTTP Only Cookie Analyzer

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions