<p>Problem Scenario:
OKD cluster is having two cluster-admins: User1 and User2.</p>

<p>If User1 connects to cluster using ssh and performs <code>oc login</code> and parallely User2 connects to the same cluster with new ssh session and performs <code>oc login</code>.</p>

<p>Now when User1 checks <code>oc whoami</code> the result will be <code>User2</code> (which is desired to have <code>User1</code>).  This will create problems like User1 operations(ex:deployements) to clash with User2.</p>

<p>How can this problem be eliminated so that two users can parallelly use the cluster?  </p>

<p>Note: Both User1 and User2 are configured with LDAP, is this creating problem?</p>

<blockquote>
  <p>How can this problem be eliminated so that two users can parallelly use the cluster?</p>
</blockquote>

<p>AFAIK, the OKD session is saved in $HOME/.kube/config by default. So it depends on a OS account session. If you'd like to use  at the same time, then you should use different OS account each other. OR you should run oc login --config context_file_path per each execution for saving session to different context file. Refer <a href="https://docs.okd.io/latest/cli_reference/manage_cli_profiles.html#loading-and-merging-rules" rel="nofollow noreferrer">Loading and Merging Rules
</a> for more details.</p>

<blockquote>
  <p>Note: Both User1 and User2 are configured with LDAP, is this creating problem?</p>
</blockquote>

<p>No. Identity provider configuration does not affect this.</p>
