PostgreSQL permissionsPostgreSQL roles versus users, grant permissionsFinding AD group permissions...

Branching points detection in processed image

Lost citations on Scholar

Finding Gaps in Date Ranges

Is candidate anonymity at all practical?

What's the relationship between the chords Cmaj Dmaj Emaj?

Why do we charge our flashes?

Why don't the fuse connections in programmable ROM cause the whole matrix to be shorted together?

How can a variadic template be used to generate a left-associative expression (aka left fold) in c++11?

Taking an academic pseudonym?

Does a star need to be inside a galaxy?

Who, if anyone, was the first astronaut to return to earth in a different vessel?

This Website Needs More Cat Pictures?

A dragon's soul trapped in a ring of mind shielding wants a new body; what magic could enable her to do so?

Candle stand modeling question

Why is it a problem for Freddie if the guys from Munich did what he wanted?

Animate an airplane in Beamer

Is the "hot network questions" element on Stack Overflow a dark pattern?

How to know if I am a 'Real Developer'

What does paperwork mean in this sentence?

Why, in A Midsummer Night's Dream, does "square" means "quarrel"?

How do I add numbers from two txt files with Bash?

Found a major flaw in paper from home university – to which I would like to return

Drawing a function without knowing its definition

Why is Shelob evil?



PostgreSQL permissions


PostgreSQL roles versus users, grant permissionsFinding AD group permissions sourceGrant permissions on stored procedureDefault connect rightsDeny dbo schema permissionpostgres 9.1: role public does not existHow can I grant permissions on tables created in the future to members of a particular role?Setting up a simple “permissions architecture” in PostgreSQLPostgreSQL - Grant privileges as superuserSQL Server database level roles for creating tables













1















I'm trying to achieve a simple architecture:




  1. An organization has many users

  2. A user belongs to many organizations

  3. A user can connect

  4. A user can join and leave an organization

  5. A user can read-only tables granted to organizations


First, securing permissions, as recommended in many places (https://ankane.org/postgres-users, https://marcyes.com/2016/0922-messing-with-postgresql-users-and-permissions/)



REVOKE ALL ON DATABASE stamped_development FROM PUBLIC;
REVOKE ALL ON SCHEMA public FROM PUBLIC;


Then, creating an organizations role with read permissions:



CREATE ROLE organizations;
GRANT USAGE ON SCHEMA public TO organizations;
GRANT SELECT ON ALL TABLES in SCHEMA public TO organizations;


Then, creating a users role with connect permissions:



CREATE ROLE users WITH LOGIN;
GRANT CONNECT ON DATABASE stamped_development TO users;


Create an organization and a user:



CREATE ROLE org_123 IN ROLE organizations;
CREATE ROLE user_123 WITH NOINHERIT ENCRYPTED PASSWORD 'secret' IN ROLE users;


Joining and leaving organizations as a user:



GRANT org_123 TO user_123;
REVOKE org_123 FROM user_123;


Problems:





  • psql -U user_123 -w secret fails with: role "user_123" is not permitted to log in

  • at some point I've been able to login, but couldn't read tables


Any thoughts on what's missing?










share|improve this question







New contributor




Philippe Dionne is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    1















    I'm trying to achieve a simple architecture:




    1. An organization has many users

    2. A user belongs to many organizations

    3. A user can connect

    4. A user can join and leave an organization

    5. A user can read-only tables granted to organizations


    First, securing permissions, as recommended in many places (https://ankane.org/postgres-users, https://marcyes.com/2016/0922-messing-with-postgresql-users-and-permissions/)



    REVOKE ALL ON DATABASE stamped_development FROM PUBLIC;
    REVOKE ALL ON SCHEMA public FROM PUBLIC;


    Then, creating an organizations role with read permissions:



    CREATE ROLE organizations;
    GRANT USAGE ON SCHEMA public TO organizations;
    GRANT SELECT ON ALL TABLES in SCHEMA public TO organizations;


    Then, creating a users role with connect permissions:



    CREATE ROLE users WITH LOGIN;
    GRANT CONNECT ON DATABASE stamped_development TO users;


    Create an organization and a user:



    CREATE ROLE org_123 IN ROLE organizations;
    CREATE ROLE user_123 WITH NOINHERIT ENCRYPTED PASSWORD 'secret' IN ROLE users;


    Joining and leaving organizations as a user:



    GRANT org_123 TO user_123;
    REVOKE org_123 FROM user_123;


    Problems:





    • psql -U user_123 -w secret fails with: role "user_123" is not permitted to log in

    • at some point I've been able to login, but couldn't read tables


    Any thoughts on what's missing?










    share|improve this question







    New contributor




    Philippe Dionne is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      1












      1








      1








      I'm trying to achieve a simple architecture:




      1. An organization has many users

      2. A user belongs to many organizations

      3. A user can connect

      4. A user can join and leave an organization

      5. A user can read-only tables granted to organizations


      First, securing permissions, as recommended in many places (https://ankane.org/postgres-users, https://marcyes.com/2016/0922-messing-with-postgresql-users-and-permissions/)



      REVOKE ALL ON DATABASE stamped_development FROM PUBLIC;
      REVOKE ALL ON SCHEMA public FROM PUBLIC;


      Then, creating an organizations role with read permissions:



      CREATE ROLE organizations;
      GRANT USAGE ON SCHEMA public TO organizations;
      GRANT SELECT ON ALL TABLES in SCHEMA public TO organizations;


      Then, creating a users role with connect permissions:



      CREATE ROLE users WITH LOGIN;
      GRANT CONNECT ON DATABASE stamped_development TO users;


      Create an organization and a user:



      CREATE ROLE org_123 IN ROLE organizations;
      CREATE ROLE user_123 WITH NOINHERIT ENCRYPTED PASSWORD 'secret' IN ROLE users;


      Joining and leaving organizations as a user:



      GRANT org_123 TO user_123;
      REVOKE org_123 FROM user_123;


      Problems:





      • psql -U user_123 -w secret fails with: role "user_123" is not permitted to log in

      • at some point I've been able to login, but couldn't read tables


      Any thoughts on what's missing?










      share|improve this question







      New contributor




      Philippe Dionne is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.












      I'm trying to achieve a simple architecture:




      1. An organization has many users

      2. A user belongs to many organizations

      3. A user can connect

      4. A user can join and leave an organization

      5. A user can read-only tables granted to organizations


      First, securing permissions, as recommended in many places (https://ankane.org/postgres-users, https://marcyes.com/2016/0922-messing-with-postgresql-users-and-permissions/)



      REVOKE ALL ON DATABASE stamped_development FROM PUBLIC;
      REVOKE ALL ON SCHEMA public FROM PUBLIC;


      Then, creating an organizations role with read permissions:



      CREATE ROLE organizations;
      GRANT USAGE ON SCHEMA public TO organizations;
      GRANT SELECT ON ALL TABLES in SCHEMA public TO organizations;


      Then, creating a users role with connect permissions:



      CREATE ROLE users WITH LOGIN;
      GRANT CONNECT ON DATABASE stamped_development TO users;


      Create an organization and a user:



      CREATE ROLE org_123 IN ROLE organizations;
      CREATE ROLE user_123 WITH NOINHERIT ENCRYPTED PASSWORD 'secret' IN ROLE users;


      Joining and leaving organizations as a user:



      GRANT org_123 TO user_123;
      REVOKE org_123 FROM user_123;


      Problems:





      • psql -U user_123 -w secret fails with: role "user_123" is not permitted to log in

      • at some point I've been able to login, but couldn't read tables


      Any thoughts on what's missing?







      postgresql permissions






      share|improve this question







      New contributor




      Philippe Dionne is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question







      New contributor




      Philippe Dionne is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question






      New contributor




      Philippe Dionne is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 7 hours ago









      Philippe DionnePhilippe Dionne

      61




      61




      New contributor




      Philippe Dionne is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      Philippe Dionne is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      Philippe Dionne is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          1 Answer
          1






          active

          oldest

          votes


















          1














          You created user_123 with the noinherit option, which means that none of the privileges granted to the role users (in which you created user_123) applies to the new role.



          And the organization role org_123 also does not have the connect privilege, so your user does not have any connect privilege at all.



          You want:



          CREATE ROLE user_123 WITH PASSWORD 'secret' IN ROLE users;


          That way all privileges from users are granted to role user_123






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "182"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });






            Philippe Dionne is a new contributor. Be nice, and check out our Code of Conduct.










            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f230096%2fpostgresql-permissions%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1














            You created user_123 with the noinherit option, which means that none of the privileges granted to the role users (in which you created user_123) applies to the new role.



            And the organization role org_123 also does not have the connect privilege, so your user does not have any connect privilege at all.



            You want:



            CREATE ROLE user_123 WITH PASSWORD 'secret' IN ROLE users;


            That way all privileges from users are granted to role user_123






            share|improve this answer




























              1














              You created user_123 with the noinherit option, which means that none of the privileges granted to the role users (in which you created user_123) applies to the new role.



              And the organization role org_123 also does not have the connect privilege, so your user does not have any connect privilege at all.



              You want:



              CREATE ROLE user_123 WITH PASSWORD 'secret' IN ROLE users;


              That way all privileges from users are granted to role user_123






              share|improve this answer


























                1












                1








                1







                You created user_123 with the noinherit option, which means that none of the privileges granted to the role users (in which you created user_123) applies to the new role.



                And the organization role org_123 also does not have the connect privilege, so your user does not have any connect privilege at all.



                You want:



                CREATE ROLE user_123 WITH PASSWORD 'secret' IN ROLE users;


                That way all privileges from users are granted to role user_123






                share|improve this answer













                You created user_123 with the noinherit option, which means that none of the privileges granted to the role users (in which you created user_123) applies to the new role.



                And the organization role org_123 also does not have the connect privilege, so your user does not have any connect privilege at all.



                You want:



                CREATE ROLE user_123 WITH PASSWORD 'secret' IN ROLE users;


                That way all privileges from users are granted to role user_123







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 4 hours ago









                a_horse_with_no_namea_horse_with_no_name

                39.9k776112




                39.9k776112






















                    Philippe Dionne is a new contributor. Be nice, and check out our Code of Conduct.










                    draft saved

                    draft discarded


















                    Philippe Dionne is a new contributor. Be nice, and check out our Code of Conduct.













                    Philippe Dionne is a new contributor. Be nice, and check out our Code of Conduct.












                    Philippe Dionne is a new contributor. Be nice, and check out our Code of Conduct.
















                    Thanks for contributing an answer to Database Administrators Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f230096%2fpostgresql-permissions%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Anexo:Material bélico de la Fuerza Aérea de Chile Índice Aeronaves Defensa...

                    Always On Availability groups resolving state after failover - Remote harden of transaction...

                    update json value to null Announcing the arrival of Valued Associate #679: Cesar Manara ...