Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
cloudappliance/cifs [2020_06_18 02:37] – [CIFS/SMB Connector (Multi User)] steven | cloudappliance/cifs [2020_08_24 11:54] – dan | ||
---|---|---|---|
Line 1: | Line 1: | ||
# CIFS/SMB Connector (Multi User) | # CIFS/SMB Connector (Multi User) | ||
- | == Last updated on June 15, 2020 == | + | == Last updated on August 24, 2020 == |
//(New in 1906.07 - Appliance Only)// | //(New in 1906.07 - Appliance Only)// | ||
+ | |||
+ | <WRAP center round important 100%> | ||
+ | We recommend using this connector with v1906.08 or higher of the File Fabric. | ||
+ | </ | ||
+ | |||
+ | |||
+ | For the single-user CIFS/SMB connector [[cloudappliance: | ||
===== Overview ===== | ===== Overview ===== | ||
- | The CIFS/SMB connector provides end-users with access to their data stored within the CIFS/SMB shares via the Enterprise File Fabric and its' multiple channels of access, including web, desktop, and mobile. | + | The CIFS/SMB connector provides end-users with access to their data stored within the CIFS/SMB shares via the Enterprise File Fabric and its' multiple channels of access, including web, desktop, and mobile. This can be CIFS shared that are on-premises, |
The connector binds Identity and Access Management from the Enterprise File Fabric (integrated via Active Directory / LDAP integration) with the permissions of the underlying file shares to provide users with secure access into the SMB storage, whilst ensuring that users only see and access data that they have permissions to from the underlying shares. | The connector binds Identity and Access Management from the Enterprise File Fabric (integrated via Active Directory / LDAP integration) with the permissions of the underlying file shares to provide users with secure access into the SMB storage, whilst ensuring that users only see and access data that they have permissions to from the underlying shares. | ||
Line 39: | Line 46: | ||
/ / | / / | ||
- | * **Protocol version** - This is used to control the SMB protocol version that is used. As of writing, **3.0** is the most secure and most recommended version to use. | + | * **Protocol version** - This is used to control the SMB protocol version that is used. As of writing, **3.0** is the most secure and most recommended version to use. <WRAP center round important 100%> |
+ | It appears that some implementations of SMB 3.0 with ABE don't work as expected. | ||
+ | </ | ||
* **Use SMBClient for Listing** - Using the smbclient can have performance benefits and is recommended. | * **Use SMBClient for Listing** - Using the smbclient can have performance benefits and is recommended. | ||
Line 73: | Line 83: | ||
var $cifsldapcachetime = 300; | var $cifsldapcachetime = 300; | ||
``` | ``` | ||
+ | |||
+ | <WRAP center round help 100%> | ||
+ | For guidance in adding, modifying, or deleting configuration parameters, [[appliance/ | ||
+ | |||
* The EFF will automatically manage specific mount points on the EFF host machine. Operations performed by users, such as opening, editing and sharing are performed on the individual user's mounts. This underpins the security of the connector. | * The EFF will automatically manage specific mount points on the EFF host machine. Operations performed by users, such as opening, editing and sharing are performed on the individual user's mounts. This underpins the security of the connector. | ||
* It is recommended to have the following configuration option enabled: | * It is recommended to have the following configuration option enabled: | ||
Line 80: | Line 94: | ||
``` | ``` | ||
* If a user receives the message " | * If a user receives the message " | ||
- | * It is recommended on the first setup to add this connector using your Organization Admin account, and not a ' | ||
- | For guidance | + | * The baseDN that you specify for LDAP searches must be high enough |
+ | |||
+ | * If the password of a user who is using the File Fabric' | ||
+ | |||
+ | * Share names configured in the File Fabric must match the corresponding names on the storage exactly, including case. If the cases differ then you will experience errors when adding the provider. | ||
+ | * When a folder is being configured as the root of a share, the full folder path configured in the File Fabric must match the path on the storage exactly, including case. If there are differences in case then the File Fabric will not be able to fetch and use the storage' | ||