UID/GID Mapping: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m (→Introduction: reference projids) |
||
| Line 1: | Line 1: | ||
=== Introduction === | === Introduction === | ||
Using Nodemap, UIDs and | Using Nodemap, UIDs, GIDs and PROJIDs provided by remote clients can be | ||
mapped onto a local set of UIDs and | mapped onto a local set of UIDs, GIDs and PROJIDs. | ||
You may find this useful if: | You may find this useful if: | ||
* You need to prevent UID and | * You need to prevent UID, GID, and PROJID collisions between clients in different administrative domains | ||
* Two or more partner organizations would like to share data | * Two or more partner organizations would like to share data | ||
* You can limit access from a partner site | * You can limit access from a partner site | ||
Revision as of 17:26, 5 March 2023
Introduction
Using Nodemap, UIDs, GIDs and PROJIDs provided by remote clients can be mapped onto a local set of UIDs, GIDs and PROJIDs.
You may find this useful if:
- You need to prevent UID, GID, and PROJID collisions between clients in different administrative domains
- Two or more partner organizations would like to share data
- You can limit access from a partner site