linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bfields@fieldses.org (J. Bruce Fields)
To: mrsvd1v4rgo1@airpost.net
Cc: linux-nfs@vger.kernel.org
Subject: Re: Help with user ID mapping?
Date: Wed, 15 Aug 2018 14:36:28 -0400	[thread overview]
Message-ID: <20180815183628.GA29569@fieldses.org> (raw)
In-Reply-To: <1533838052.2201783.1469033928.4B670F71@webmail.messagingengine.com>

On Thu, Aug 09, 2018 at 11:07:32AM -0700, mrsvd1v4rgo1@airpost.net wrote:
> I'm trying to get a NFS4 client & server id mapping working right.
> 
> My client mounts to a couple of NFS4 servers.
> 
> I want to get it setup so that for just ONE of them, files added to or
> modified on the server BY my local client, logged in EITHER as my user
> or root, get written with a specific user/group ==  "nobody:users"

You should be able to do that by just adding "all_squash" to the export
options in /etc/exports for that one client.

> I'm pretty sure that all the magic is done with idmapd config.

This is a common source of confusion.  NFSv4 idmapping only deals with
names and IDs that are sent in NFSv4 protocol messages--when setting or
getting file owners and groups, or ACLs.

It's the underlying RPC protocol that tells the server who is performing
a given RPC.  That always uses numeric IDs or krb5 principals, and isn't
affected by anything in idmapd.conf.

--b.

      reply	other threads:[~2018-08-15 21:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-09 18:07 Help with user ID mapping? mrsvd1v4rgo1
2018-08-15 18:36 ` J. Bruce Fields [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180815183628.GA29569@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=mrsvd1v4rgo1@airpost.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).