Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Create and access a list of your products

ECS 3.6.1 Administration Guide

Working with user/group mappings in the ECS Portal

You can use the User/Group Mapping tab on the File page available from Manage > File to view the existing mappings between ECS object users/groups and Unix users, to create new user/group mappings, and to edit mappings.

The User/Group Mapping tab has a Namespace field that allows you to select the namespace for which you want to see the configured user/group mappings.

ECS stores the owner and group for the bucket, and the owner and group for files and directories within the bucket, as ECS object username and custom group names, respectively. The names must be mapped to Unix IDs in order that NFS users can be given access with the appropriate privileges.

The mapping enables ECS to treat an ECS object user and an NFS user as the same user but with two sets of credentials, one to access ECS using NFS, and one to access the ECS using the object protocols. Because the accounts are mapped, files written by an NFS user will be accessible as objects by the mapped object user and objects written by the object users will be accessible as files by the NFS user.

The permissions associated with the file or object will be based on a mapping between POSIX and object protocol ACL privileges. For more information, see Multi-protocol access permissions.

Field Description
User/Group Name The object username of the user.
ID The Unix User ID or Group ID that has been mapped to the object user.
Type Indicates whether the ID is for a User or Group.
Actions The actions that can be completed on the user or group mapping. They are: View and Delete

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\