<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Push source code to gitlab using PSMP in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/push-source-code-to-gitlab-using-psmp/m-p/1418787#M87399</link>
    <description>&lt;P&gt;Sure, I've done it. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1st, generate and register your SSH key for the GitLab user as normal.&lt;/P&gt;&lt;P&gt;2nd, onboard it to PAM as a Unix SSH Key account. The username should be "git", and the address... the GitLab instance address. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then you have some choices for how to manage performing connections via the PSMP. I've opted to include the following in the SSH clients configuration: &lt;/P&gt;&lt;CODE&gt;Host gitlab.company.example
    Hostname proxy-xx.company.example
    User     "vaultuser@git@gitlab.company.example"
    IdentityFile ~/.ssh/id_pam
    IdentitiesOnly yes&lt;/CODE&gt;&lt;P&gt;Keep in mind that I use the MFA caching feature for PSMP auth. With this config in place, you can for example clone a repo like this:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;CODE&gt;$ git clone gitlab.company.example:cedric/my-repo.git
&amp;nbsp;
Cloning into 'my-repo...
&amp;nbsp;
This session is being recorded
&amp;nbsp;
remote: Enumerating objects: 12, done.
remote: Counting objects: 100% (9/9), done.
remote: Compressing objects: 100% (9/9), done.
remote: Total 12 (delta 0), reused 0 (delta 0), pack-reused 3 (from 1)
Receiving objects: 100% (12/12), 7.22 KiB | 7.22 MiB/s, done.&lt;/CODE&gt;&lt;P&gt;Subsequent actions reuse the username and stuff, so they work seamlessly. &lt;/P&gt;&lt;CODE&gt;$ git pull
&amp;nbsp;
This session is being recorded
&amp;nbsp;
Already up to date.&lt;/CODE&gt;&lt;P&gt;&amp;nbsp;Depending on your authN mechanism you'll have to manage ssh key validity and things, though, so keep that in mind.&lt;/P&gt;</description>
    <pubDate>Mon, 14 Sep 2026 11:06:00 GMT</pubDate>
    <dc:creator>C.Trost320761</dc:creator>
    <dc:date>2026-09-14T11:06:00Z</dc:date>
    <item>
      <title>Push source code to gitlab using PSMP</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/push-source-code-to-gitlab-using-psmp/m-p/1418786#M87398</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any ideas or suggestions on leveraging PSMP while pushing the source to gitlab/remote repository?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 14 Sep 2026 06:06:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/push-source-code-to-gitlab-using-psmp/m-p/1418786#M87398</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-09-14T06:06:58Z</dc:date>
    </item>
    <item>
      <title>Re: Push source code to gitlab using PSMP</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/push-source-code-to-gitlab-using-psmp/m-p/1418787#M87399</link>
      <description>&lt;P&gt;Sure, I've done it. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1st, generate and register your SSH key for the GitLab user as normal.&lt;/P&gt;&lt;P&gt;2nd, onboard it to PAM as a Unix SSH Key account. The username should be "git", and the address... the GitLab instance address. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then you have some choices for how to manage performing connections via the PSMP. I've opted to include the following in the SSH clients configuration: &lt;/P&gt;&lt;CODE&gt;Host gitlab.company.example
    Hostname proxy-xx.company.example
    User     "vaultuser@git@gitlab.company.example"
    IdentityFile ~/.ssh/id_pam
    IdentitiesOnly yes&lt;/CODE&gt;&lt;P&gt;Keep in mind that I use the MFA caching feature for PSMP auth. With this config in place, you can for example clone a repo like this:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;CODE&gt;$ git clone gitlab.company.example:cedric/my-repo.git
&amp;nbsp;
Cloning into 'my-repo...
&amp;nbsp;
This session is being recorded
&amp;nbsp;
remote: Enumerating objects: 12, done.
remote: Counting objects: 100% (9/9), done.
remote: Compressing objects: 100% (9/9), done.
remote: Total 12 (delta 0), reused 0 (delta 0), pack-reused 3 (from 1)
Receiving objects: 100% (12/12), 7.22 KiB | 7.22 MiB/s, done.&lt;/CODE&gt;&lt;P&gt;Subsequent actions reuse the username and stuff, so they work seamlessly. &lt;/P&gt;&lt;CODE&gt;$ git pull
&amp;nbsp;
This session is being recorded
&amp;nbsp;
Already up to date.&lt;/CODE&gt;&lt;P&gt;&amp;nbsp;Depending on your authN mechanism you'll have to manage ssh key validity and things, though, so keep that in mind.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Sep 2026 11:06:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/push-source-code-to-gitlab-using-psmp/m-p/1418787#M87399</guid>
      <dc:creator>C.Trost320761</dc:creator>
      <dc:date>2026-09-14T11:06:00Z</dc:date>
    </item>
  </channel>
</rss>

