Chromium web browser: user specific /etc/chromium/policies/managed/ policy file












1















I am helping with the set up of a Linux-based Library kiosk thin client solution. We are using Chromium for the web browser, which is launched by a shell script with various command line options. There are a few different use cases e.g. one for accessing the Library catalogue and a few other sites, another for making study room bookings — so we'd want independent URL whitelists. Each use case has its own command line options. Currently all whitelist URLs are stored in the file /etc/chromium/policies/managed/policy.json. Ideally I'd like to separate these out i.e. be able to add a command line option like:



--managed-policy-file=/home/libcat/.config/chromium-browser/policies/managed/policy-libcat.json


...so that each use case has its own white list. However, according to http://peter.sh/experiments/chromium-command-line-switches no such command line option exists.



Does anyone have any suggestions as to how might it be possible to make Chromium use a different policy file for each use case?










share|improve this question





























    1















    I am helping with the set up of a Linux-based Library kiosk thin client solution. We are using Chromium for the web browser, which is launched by a shell script with various command line options. There are a few different use cases e.g. one for accessing the Library catalogue and a few other sites, another for making study room bookings — so we'd want independent URL whitelists. Each use case has its own command line options. Currently all whitelist URLs are stored in the file /etc/chromium/policies/managed/policy.json. Ideally I'd like to separate these out i.e. be able to add a command line option like:



    --managed-policy-file=/home/libcat/.config/chromium-browser/policies/managed/policy-libcat.json


    ...so that each use case has its own white list. However, according to http://peter.sh/experiments/chromium-command-line-switches no such command line option exists.



    Does anyone have any suggestions as to how might it be possible to make Chromium use a different policy file for each use case?










    share|improve this question



























      1












      1








      1








      I am helping with the set up of a Linux-based Library kiosk thin client solution. We are using Chromium for the web browser, which is launched by a shell script with various command line options. There are a few different use cases e.g. one for accessing the Library catalogue and a few other sites, another for making study room bookings — so we'd want independent URL whitelists. Each use case has its own command line options. Currently all whitelist URLs are stored in the file /etc/chromium/policies/managed/policy.json. Ideally I'd like to separate these out i.e. be able to add a command line option like:



      --managed-policy-file=/home/libcat/.config/chromium-browser/policies/managed/policy-libcat.json


      ...so that each use case has its own white list. However, according to http://peter.sh/experiments/chromium-command-line-switches no such command line option exists.



      Does anyone have any suggestions as to how might it be possible to make Chromium use a different policy file for each use case?










      share|improve this question
















      I am helping with the set up of a Linux-based Library kiosk thin client solution. We are using Chromium for the web browser, which is launched by a shell script with various command line options. There are a few different use cases e.g. one for accessing the Library catalogue and a few other sites, another for making study room bookings — so we'd want independent URL whitelists. Each use case has its own command line options. Currently all whitelist URLs are stored in the file /etc/chromium/policies/managed/policy.json. Ideally I'd like to separate these out i.e. be able to add a command line option like:



      --managed-policy-file=/home/libcat/.config/chromium-browser/policies/managed/policy-libcat.json


      ...so that each use case has its own white list. However, according to http://peter.sh/experiments/chromium-command-line-switches no such command line option exists.



      Does anyone have any suggestions as to how might it be possible to make Chromium use a different policy file for each use case?







      linux chrome






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jul 30 '15 at 14:40







      Jimadine

















      asked Jul 17 '15 at 8:34









      JimadineJimadine

      1165




      1165






















          1 Answer
          1






          active

          oldest

          votes


















          0














          Two options come to mind:




          • Install chromium into separate chroot environments.


          • Put first use case file in place, fire up chrome, wait a few seconds for it to load; put second use case file in place ...Won't work; Chromium is watching the directory for changes.






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "106"
            };
            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
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f216678%2fchromium-web-browser-user-specific-etc-chromium-policies-managed-policy-file%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









            0














            Two options come to mind:




            • Install chromium into separate chroot environments.


            • Put first use case file in place, fire up chrome, wait a few seconds for it to load; put second use case file in place ...Won't work; Chromium is watching the directory for changes.






            share|improve this answer




























              0














              Two options come to mind:




              • Install chromium into separate chroot environments.


              • Put first use case file in place, fire up chrome, wait a few seconds for it to load; put second use case file in place ...Won't work; Chromium is watching the directory for changes.






              share|improve this answer


























                0












                0








                0







                Two options come to mind:




                • Install chromium into separate chroot environments.


                • Put first use case file in place, fire up chrome, wait a few seconds for it to load; put second use case file in place ...Won't work; Chromium is watching the directory for changes.






                share|improve this answer













                Two options come to mind:




                • Install chromium into separate chroot environments.


                • Put first use case file in place, fire up chrome, wait a few seconds for it to load; put second use case file in place ...Won't work; Chromium is watching the directory for changes.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Sep 23 '17 at 20:19









                K3---rncK3---rnc

                1,9421119




                1,9421119






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Unix & Linux 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%2funix.stackexchange.com%2fquestions%2f216678%2fchromium-web-browser-user-specific-etc-chromium-policies-managed-policy-file%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

                    How to reconfigure Docker Trusted Registry 2.x.x to use CEPH FS mount instead of NFS and other traditional...

                    is 'sed' thread safe

                    How to make a Squid Proxy server?