Project Did Not Get Inherited Correctly When Logging In Using Ssh Key Authentication (Doc ID 1376628.1)

Last updated on JULY 29, 2016

Applies to:

Solaris Operating System - Version 10 3/05 to 10 1/13 U11 [Release 10.0]
Information in this document applies to any platform.
***Checked for relevance on 17-Dec-2013***

Symptoms

A project had been configured for a user. When the user would use ssh to connect to the system, the project ID was not being properly set.

For example the configuration and id -p outputs:

1. Created a project for "user1":

# projadd -U user -K "project.max-shm-memory=(priv,4096MB,deny)" user.user1

 

# prctl -n project.max-shm-memory -i project 102
project: 102: user.user1
NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT
project.max-shm-memory
privileged 4.00GB - deny -
system 16.0EB max deny



2. Logging in via ssh using the "user1" account. The project id "0" (system) is assigned and not project id "102" (user.user1):

login as: user1
Authenticating with public key "rsa-key-20100208" from agent
Last login: Thu Nov 3 08:25:54 2011 from 10.79.116.62
Oracle Corporation SunOS 5.10 Generic Patch January 2005
$ id -p
uid=5009(user1) gid=1000(admin) projid=0(system)



3. If a su - user1 is done after making the ssh connection, project id "102" (user.user1) is now assigned:

$ su - user1
Password:
Oracle Corporation SunOS 5.10 Generic Patch January 2005
$ id -p
uid=5009(user1) gid=1000(admin) projid=102(user.user1)



Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms