<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Actually - that's excellent - it's working like I thought it
      should now! <br>
    </p>
    <p>Thanks - I had been looking at this way too long and ignoring the
      fact I could make the authcfg whatever I wanted! So I was stuck on
      changing it when I just needed to set it up differently. <br>
    </p>
    <p><br>
      Randy<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 02/05/2018 01:06 PM, Alessandro
      Pasotti wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAL5Q671kzRMfYD8oEQbQ0=DKgZHWupA-5X3c4QFoXwi_0qnoYQ@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">On Mon, Feb 5, 2018 at 6:57 PM,
            Randal Hale <span dir="ltr"><<a
                href="mailto:rjhale@northrivergeographic.com"
                target="_blank" moz-do-not-send="true">rjhale@northrivergeographic.com</a>></span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div text="#000000" bgcolor="#FFFFFF">
                <p>I'm not entirely sure I've titled this correctly. <br>
                </p>
                <p>I have a client that has about 20 people editing.
                  There is a want to reduce editing pain by introducing
                  dropdown lists in the form of widgets. <br>
                </p>
                <ul>
                  <li>20 users have 20 logins to the postgres/postgis
                    database <br>
                  </li>
                  <li>20 users have 20 qgs files which need to be
                    replaced<br>
                  </li>
                </ul>
                <p>My first thought to "fix" some of the headache was
                  using the Authentification manager. I would have
                  everyone set that up and I could build the qgs files
                  and pass them along. They would open them and be asked
                  for a password. The Authentification manager passes
                  their credentials back to the database. It replaces
                  the authcfg in the project with theirs and life is
                  good. <br>
                </p>
                <p>What I am finding is that my layers which have an
                  Auth-id of xxxxxxx never get replaced by the Auth-id
                  of their machine of yyyyyyyy - so every time they open
                  my new qgs file they are prompted for the password of
                  the authcfg database and their connection credentials.
                  Which - maybe that's the way it works and not the way
                  I think (which is generally not the way the world
                  works). <br>
                </p>
                <p>example: <i>dbname='client_database' host=gis4 port
                    5432 sslmode=disable authcfg=<b>938s81lr</b>
                    key='id' srid=2274 type=multilinestring
                    table="fiber.m_fiber" (geom) sql=</i></p>
                <p><i>Their authcfg is not</i><b><i> 938s81lr. </i></b><i>It
                    never gets replaced<b> </b>with their <b>authcfg</b></i><b><i><br>
                    </i></b></p>
                <p>Is there a way to replace authcfg with their authcfg
                  which would let me cascade these new QGIS files to the
                  users? I could eliminate three things that must be
                  typed down to one upon opening the file. <br>
                </p>
                <p>Thanks much! Hopefully this all makes some sense. <br>
                </p>
                <p>Randy<span class="HOEnZb"><font color="#888888"><br>
                    </font></span></p>
                <span class="HOEnZb"><font color="#888888">
                    <p><br>
                    </p>
                  </font></span><br>
              </div>
            </blockquote>
          </div>
          <br>
          <br>
        </div>
        <div class="gmail_extra">Hi, maybe I misunderstood your needs
          but I don't see the issue.<br>
          <br>
        </div>
        <div class="gmail_extra">The authcfg is just an ID that the QGIS
          authentication manager uses to retrieve the credentials from
          the QGIS user authentication DB.<br>
          <br>
        </div>
        <div class="gmail_extra">If I get your point, what I suggest you
          is that you create your project (the one that needs to be
          distributed) and configure your layers with a custom authcfg
          (you can use up to 7 digits or letters to name it) and just
          tell the users to create an entry in their authentication DB
          (using the authentication manager in their QGIS instance) with
          same authcfg that you have chosen and  with their credentials.<br>
          <br>
        </div>
        <div class="gmail_extra">Hope that helps!<br>
        </div>
        <div class="gmail_extra"><br>
          -- <br>
          <div class="gmail_signature" data-smartmail="gmail_signature">Alessandro
            Pasotti<br>
            w3:   <a href="http://www.itopen.it" target="_blank"
              moz-do-not-send="true">www.itopen.it</a></div>
        </div>
      </div>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Randal Hale 
<a class="moz-txt-link-abbreviated" href="mailto:rjhale@northrivergeographic.com">rjhale@northrivergeographic.com</a>
<a class="moz-txt-link-freetext" href="https://www.northrivergeographic.com">https://www.northrivergeographic.com</a>
(423)653-3611

</pre>
  </body>
</html>