IBM Support

Understanding NOBODY in the credmap output

Question & Answer


Question

Why does NOBODY appear in the credmap output if the usernames and groups do not match when I'm trying to configure IBM® Rational® ClearCase® Interoperation (Interop) with Microsoft® Windows®, UNIX® and Linux®?

Answer

The supported Rational ClearCase Interop configuration requires that the user's username and primary group name are identical on Windows and UNIX (and or Linux), refer to technote 1146784 for more details.

In an interop environment, where a user's username and or primary group does not match then NOBODY gets reported in the credmap output to identify the discrepancy.

This is true whether you have configured Windows clients to access UNIX VOBs or if you have configured UNIX clients to access Windows VOBs (technote 1141329).

The credmap utility is available on both Windows and UNIX, run cleartool man credmap for more details on this utility.



Example:

The user's username matches on both operating systems, but the primary group does not. Therefore, the Primary group on Windows is set to Domain\ccusers, and the Primary group SID on UNIX is set to NOBODY.

Identity on local system:
User: Domain\user1 (NT:S-1-5-21-2106544897-1487...)
Primary group: Domain\ccusers (NT:S-1-5-21-2106544897-14...)
Groups: (7)
Everyone (NT:S-1-1-0)
BUILTIN\Administrators (NT:S-1-5-32-544)
BUILTIN\Power Users (NT:S-1-5-32-547)
BUILTIN\Users (NT:S-1-5-32-545)
NT AUTHORITY\INTERACTIVE (NT:S-1-5-4)
NT AUTHORITY\Authenticated Users (NT:S-1-5-11)
LOCAL (NT:S-1-2-0)

Identity on host "UNIX_Host":
User SID: UNIX:UID-59835
Primary group SID: NOBODY
Group SID list: (2)
NOBODY
UNIX:GID-20

Note: NOBODY reported in the Groups section of the Windows output, or in the Group SID list section of the UNIX output is not a problem. This is only referring to any additional groups that the username may belong to, but those groups may not exist on both operating systems, nor is that required.



Currently, there is no alternative for the supported configuration, which requires matching usernames and primary groups.

The following change requests (RFEs) have been opened concerning the ability to have non-matching usernames and groups:

  • RATLC00588462 - Enable Microsoft Windows clients to access UNIX VOBs and Views, but not require the UNIX/Linux groups to depend on Windows groups; so they do not have to be identical.

  • RATLC00585414 - Create a CLEARCASE_USER NT environment variable to map a Windows user(name) to a UNIX/Linux user(name).


For more specifics on Rational ClearCase Network Administration in Mixed Environments, refer to the IBM Rational ClearCase Administrator's Guide.

Documentation

[{"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Interop","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF015","label":"IRIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.0;7.0.0.1;7.0.0.2;7.0.1;7.0.1.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Permissions","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
16 June 2018

UID

swg21159386