From e05e86793e8f307f0b875fe769d15db78ed6e91c Mon Sep 17 00:00:00 2001 From: lukinovec Date: Tue, 19 Jul 2022 08:57:10 +0200 Subject: [PATCH] Update the page --- source/docs/v3/tenant-attribute-encryption.blade.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/source/docs/v3/tenant-attribute-encryption.blade.md b/source/docs/v3/tenant-attribute-encryption.blade.md index 4ea994b..72ea46c 100644 --- a/source/docs/v3/tenant-attribute-encryption.blade.md +++ b/source/docs/v3/tenant-attribute-encryption.blade.md @@ -6,9 +6,11 @@ section: content # Tenant attribute encryption {#encrypt} -To encrypt the attributes, you must store them in [custom columns](https://tenancyforlaravel.com/docs/v3/tenants/#custom-columns). For example, we'll encrypt the tenant's database credentials (which are stored using the [Virtual Column](https://github.com/archtechx/virtualcolumn) as `tenancy_db_username` and `tenancy_db_password` by default) in a few steps. +To encrypt the tenant attributes, store them in [custom columns](https://tenancyforlaravel.com/docs/v3/tenants/#custom-columns), and on the Tenant model, cast the attributes you want to encrypt to `'encrypted'`, or use your custom encryption cast. -Add custom columns to the tenants migration (we recommend making the string size at least 512 characters, so it's big enough to contain the encrypted data): +For example, we'll encrypt the tenant's database credentials – `tenancy_db_username` and `tenancy_db_password`. We need to create custom columns for these attributes, because they are, by default, stored using [virtual column](https://github.com/archtechx/virtualcolumn). + +- Add custom columns to the tenants migration (we recommend making the string size at least 512 characters, so the string is capable of containing the encrypted data): ```php