stancl/tenancy-docs
1
0
Fork 0
mirror of https://github.com/stancl/tenancy-docs.git synced 2025-12-12 18:24:03 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Make the links work (+ automatic formatting correction)

Browse source
This commit is contained in:
lukinovec 2022-08-01 08:14:05 +02:00
parent 01d65793c0
commit 8cf0033793
1 changed files with 24 additions and 24 deletions
Download patch file Download diff file Expand all files Collapse all files

12
source/docs/v3/integrations/passport.blade.md
View file

@ -21,11 +21,11 @@ section: content
- [**Shared keys**](#shared-keys) - [**Shared keys**](#shared-keys)
- [**Tenant-specific keys**](#tenant-specific-keys) - [**Tenant-specific keys**](#tenant-specific-keys)
### **Using Passport only in central application** ### **Using Passport only in central application** {#using-passport-only-in-central-application}
You don't have to do anything special in this use case, just install **Laravel Passport** as its official documentation explains: You don't have to do anything special in this use case, just install **Laravel Passport** as its official documentation explains:
[Laravel Passport official documentation](https://laravel.com/docs/9.x/passport) [Laravel Passport official documentation](https://laravel.com/docs/9.x/passport)
### **Using Passport only in tenant application** ### **Using Passport only in tenant application** {#using-passport-only-in-tenant-application}
To use **Laravel Passport** inside the tenant application, you must follow the following steps: To use **Laravel Passport** inside the tenant application, you must follow the following steps:
1. Add this code to the `register` method in your `AppServiceProvider` to prevent Passport migrations from running in the central application: 1. Add this code to the `register` method in your `AppServiceProvider` to prevent Passport migrations from running in the central application:
@ -69,7 +69,7 @@ To use **Laravel Passport** inside the tenant application, you must follow the f
6. Create Passport keys following [**Manage Passport keys**](#manage-passport-keys) section. 6. Create Passport keys following [**Manage Passport keys**](#manage-passport-keys) section.
### **Using Passport in both the central and tenant application** ### **Using Passport in both the central and tenant application** {#using-passport-in-both-the-central-and-tenant-application}
To use **Laravel Passport** on central and tenant application, you must follow the following steps: To use **Laravel Passport** on central and tenant application, you must follow the following steps:
1. Enable [**Universal Routes**]({{ $page->link('universal-routes') }}) feature. 1. Enable [**Universal Routes**]({{ $page->link('universal-routes') }}) feature.
@ -110,11 +110,11 @@ To use **Laravel Passport** on central and tenant application, you must follow t
6. Create Passport keys following [**Manage Passport keys**](#manage-passport-keys) section. 6. Create Passport keys following [**Manage Passport keys**](#manage-passport-keys) section.
### **Manage Passport keys** ### **Manage Passport keys** {#manage-passport-keys}
#### **Shared keys** #### **Shared keys** {#shared-keys}
If you want to use the same Passport keys for all your tenants and your central application (in case you are using Passport in your central app), you only have to run `php artisan passport:keys` command and you are done. If you want to use the same Passport keys for all your tenants and your central application (in case you are using Passport in your central app), you only have to run `php artisan passport:keys` command and you are done.
#### **Tenant-specific keys** #### **Tenant-specific keys** {#tenant-specific-keys}
> **Note:** The security benefit of doing this isn't probably that big, since you're likely already using the same `APP_KEY` for all tenants. This is a relatively complex approach, so before implementing it, make sure you really want it. > **Note:** The security benefit of doing this isn't probably that big, since you're likely already using the same `APP_KEY` for all tenants. This is a relatively complex approach, so before implementing it, make sure you really want it.
If you want to use an unique Passport keys for each tenant, there are multiple ways you can store and load tenant Passport keys, but the most straightforward way is to store the keys in the `Tenant model` and load them into the passport configuration using the [**Tenant Config**]({{ $page->link('features/tenant-config') }}) feature. If you want to use an unique Passport keys for each tenant, there are multiple ways you can store and load tenant Passport keys, but the most straightforward way is to store the keys in the `Tenant model` and load them into the passport configuration using the [**Tenant Config**]({{ $page->link('features/tenant-config') }}) feature.