Update passport.blade.md Regarding Passport 12 Shared Keys #289
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
docs: add note on Passport v12 key path for shared keys in tenant environment - Added a subsection under “Shared keys” explaining how to use `Passport::loadKeysFrom(storage_path())` to force Passport to load a single key pair from the central storage path for all tenants. - Helps avoid tenant-specific key path issues in Passport v12.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
docs: add note on Passport v12 key path for shared keys in tenant environment
Passport::loadKeysFrom(storage_path())to force Passport to load a single key pair from the central storage path for all tenants.This update adds a short note in the Shared keys section clarifying that Passport 12 may look for its encryption keys in a tenant-specific directory (/storage/tenant/{tenant}/...). We’ve included instructions on forcing Passport to load keys from a single shared path, ensuring all tenants use the same key files. This avoids potential issues where tenant-scoped folders do not contain their own Passport keys.