<?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 Automation script for securitization by Section Access (V2) in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Automation-script-for-securitization-by-Section-Access-V2/m-p/1751018#M57812</link>
    <description>&lt;P&gt;Hello everyone !&lt;/P&gt;&lt;P&gt;I would like to share with you my most recent work about an automation script for securitization by Section Access because &lt;SPAN&gt;I think it could be useful to anyone who struggle or spends too much time to put it in place and maintain it &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;My objective was to find a solution to the following points :&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Avoid manual entry of the section access table in the script of each application because this operation is often a source of errors and time consuming.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Industrialize the creation of the section access table with a generic script including many input and processing controls.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Harmonize the security rule entry phase using standardized and centralized Excels files.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Support new entry rules that are &lt;FONT color="#0000FF"&gt;&lt;U&gt;more convenient and powerful than default ones&lt;/U&gt;&lt;/FONT&gt;.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Automatically export a summary of the active rules for each application to facilitate security audits (optional).&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Here are the main features of the solution I was able to put in place :&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The script is designed to work with A SINGLE reduction field.&lt;BR /&gt;(Use compound keys for more complex scenarios as suggested by Qlik experts : &lt;A href="https://community.qlik.com/t5/Qlik-Design-Blog/Data-Reduction-Using-Multiple-Fields/ba-p/1474917" target="_blank" rel="noopener"&gt;https://community.qlik.com/t5/Qlik-Design-Blog/Data-Reduction-Using-Multiple-Fields/ba-p/1474917&lt;/A&gt;)&lt;/LI&gt;&lt;LI&gt;The reduction rules must be specified in an individual Excel file for each application to be secured.&lt;BR /&gt;You can specify (optional) the username of the developer/owner of the application, so that it will automatically get access to all data.&lt;/LI&gt;&lt;LI&gt;Ability to provide "permanent administrators" in a separate Excel file for which access to all values will be systematically granted across all applications.&lt;/LI&gt;&lt;LI&gt;Supported rule types (mixture possible):&lt;BR /&gt;- Individually by users&lt;BR /&gt;- By groups of QMC users referenced and synchronized from a directory (usually LDAP groups)&lt;BR /&gt;- By groups of users defined locally (useful if there is no QMC directory groups existing or simply to bypass existing ones)&lt;/LI&gt;&lt;LI&gt;Possible filtering values ​​(with examples) :&lt;/LI&gt;&lt;/UL&gt;&lt;P class="lia-indent-padding-left-60px"&gt;&lt;U&gt;&lt;STRONG&gt;Basic&lt;/STRONG&gt;&lt;/U&gt;&lt;BR /&gt;- All values: '*'&lt;BR /&gt;- Single value: 'UK'&lt;BR /&gt;- Multiple values ​​(two possible ways):&lt;BR /&gt;-&amp;gt; Across multiple lines (one value per line, the same you have to do when writing the access section table by yourself)&lt;BR /&gt;-&amp;gt; Across a single line using a specific separator : 'UK;IT;ES'&lt;/P&gt;&lt;P class="lia-indent-padding-left-60px"&gt;&lt;U&gt;&lt;STRONG&gt;Advanced&lt;/STRONG&gt;&lt;/U&gt;&lt;BR /&gt;- &lt;FONT color="#0000FF"&gt;Support for wildcards "*" and "?"&lt;/FONT&gt; in reduction values which makes it possible to write rules of the type "LIKE".&lt;BR /&gt;The creation of generic keys in the data model to satisfy more complex cases is no longer mandatory because you can use wildcard (&lt;A href="https://community.qlik.com/t5/Qlik-Design-Blog/Basics-for-complex-authorization/ba-p/1465872" target="_blank" rel="noopener"&gt;https://community.qlik.com/t5/Qlik-Design-Blog/Basics-for-complex-authorization/ba-p/1465872&lt;/A&gt;).&lt;/P&gt;&lt;P class="lia-indent-padding-left-60px"&gt;Example : the rule 'B*;U*' will grant access to all values starting with the letters 'B' and 'U'.&lt;/P&gt;&lt;P class="lia-indent-padding-left-60px"&gt;&lt;BR /&gt;- &lt;FONT color="#0000FF"&gt;Support rules in exclusion mode.&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#000000"&gt;Instead of listing the allowed values (default), now you can do the opposite by listing the prohibited values, which is much quicker to formulate in some cases.&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#000000"&gt;To do this, the value or list of values must be prefixed with "[*-]" which means "everything but".&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;Example : if dataset has 100 country codes and I wish they were all accessible EXCEPT two of them, then I can write : "[*-]UK;USA"&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Ability to hide one or more fields from the data model to a user/group.&lt;/LI&gt;&lt;LI&gt;Optional preservation of an audit table in the data model and/or export of it as a QVD file for later analysis.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;********************************************************************************************&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;All necessary files are available in the attached Zip archive.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Almost all resources are commented in both English and French (including the implementation guide) to allow anyone to use it.&lt;BR /&gt;(Only the script itself is written in French with English comments for editable settings).&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I'll be very happy to have your feedback &lt;span class="lia-unicode-emoji" title=":smiling_face_with_smiling_eyes:"&gt;😊&lt;/span&gt;&lt;BR /&gt;Don't hesitate to ask if you have any problems or to suggest improvements.&lt;/P&gt;&lt;P&gt;Have a nice day !&lt;/P&gt;</description>
    <pubDate>Sat, 16 Nov 2024 01:19:31 GMT</pubDate>
    <dc:creator>bfournet</dc:creator>
    <dc:date>2024-11-16T01:19:31Z</dc:date>
    <item>
      <title>Automation script for securitization by Section Access (V2)</title>
      <link>https://community.qlik.com/t5/App-Development/Automation-script-for-securitization-by-Section-Access-V2/m-p/1751018#M57812</link>
      <description>&lt;P&gt;Hello everyone !&lt;/P&gt;&lt;P&gt;I would like to share with you my most recent work about an automation script for securitization by Section Access because &lt;SPAN&gt;I think it could be useful to anyone who struggle or spends too much time to put it in place and maintain it &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;My objective was to find a solution to the following points :&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Avoid manual entry of the section access table in the script of each application because this operation is often a source of errors and time consuming.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Industrialize the creation of the section access table with a generic script including many input and processing controls.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Harmonize the security rule entry phase using standardized and centralized Excels files.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Support new entry rules that are &lt;FONT color="#0000FF"&gt;&lt;U&gt;more convenient and powerful than default ones&lt;/U&gt;&lt;/FONT&gt;.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Automatically export a summary of the active rules for each application to facilitate security audits (optional).&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Here are the main features of the solution I was able to put in place :&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The script is designed to work with A SINGLE reduction field.&lt;BR /&gt;(Use compound keys for more complex scenarios as suggested by Qlik experts : &lt;A href="https://community.qlik.com/t5/Qlik-Design-Blog/Data-Reduction-Using-Multiple-Fields/ba-p/1474917" target="_blank" rel="noopener"&gt;https://community.qlik.com/t5/Qlik-Design-Blog/Data-Reduction-Using-Multiple-Fields/ba-p/1474917&lt;/A&gt;)&lt;/LI&gt;&lt;LI&gt;The reduction rules must be specified in an individual Excel file for each application to be secured.&lt;BR /&gt;You can specify (optional) the username of the developer/owner of the application, so that it will automatically get access to all data.&lt;/LI&gt;&lt;LI&gt;Ability to provide "permanent administrators" in a separate Excel file for which access to all values will be systematically granted across all applications.&lt;/LI&gt;&lt;LI&gt;Supported rule types (mixture possible):&lt;BR /&gt;- Individually by users&lt;BR /&gt;- By groups of QMC users referenced and synchronized from a directory (usually LDAP groups)&lt;BR /&gt;- By groups of users defined locally (useful if there is no QMC directory groups existing or simply to bypass existing ones)&lt;/LI&gt;&lt;LI&gt;Possible filtering values ​​(with examples) :&lt;/LI&gt;&lt;/UL&gt;&lt;P class="lia-indent-padding-left-60px"&gt;&lt;U&gt;&lt;STRONG&gt;Basic&lt;/STRONG&gt;&lt;/U&gt;&lt;BR /&gt;- All values: '*'&lt;BR /&gt;- Single value: 'UK'&lt;BR /&gt;- Multiple values ​​(two possible ways):&lt;BR /&gt;-&amp;gt; Across multiple lines (one value per line, the same you have to do when writing the access section table by yourself)&lt;BR /&gt;-&amp;gt; Across a single line using a specific separator : 'UK;IT;ES'&lt;/P&gt;&lt;P class="lia-indent-padding-left-60px"&gt;&lt;U&gt;&lt;STRONG&gt;Advanced&lt;/STRONG&gt;&lt;/U&gt;&lt;BR /&gt;- &lt;FONT color="#0000FF"&gt;Support for wildcards "*" and "?"&lt;/FONT&gt; in reduction values which makes it possible to write rules of the type "LIKE".&lt;BR /&gt;The creation of generic keys in the data model to satisfy more complex cases is no longer mandatory because you can use wildcard (&lt;A href="https://community.qlik.com/t5/Qlik-Design-Blog/Basics-for-complex-authorization/ba-p/1465872" target="_blank" rel="noopener"&gt;https://community.qlik.com/t5/Qlik-Design-Blog/Basics-for-complex-authorization/ba-p/1465872&lt;/A&gt;).&lt;/P&gt;&lt;P class="lia-indent-padding-left-60px"&gt;Example : the rule 'B*;U*' will grant access to all values starting with the letters 'B' and 'U'.&lt;/P&gt;&lt;P class="lia-indent-padding-left-60px"&gt;&lt;BR /&gt;- &lt;FONT color="#0000FF"&gt;Support rules in exclusion mode.&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#000000"&gt;Instead of listing the allowed values (default), now you can do the opposite by listing the prohibited values, which is much quicker to formulate in some cases.&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#000000"&gt;To do this, the value or list of values must be prefixed with "[*-]" which means "everything but".&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;Example : if dataset has 100 country codes and I wish they were all accessible EXCEPT two of them, then I can write : "[*-]UK;USA"&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Ability to hide one or more fields from the data model to a user/group.&lt;/LI&gt;&lt;LI&gt;Optional preservation of an audit table in the data model and/or export of it as a QVD file for later analysis.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;********************************************************************************************&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;All necessary files are available in the attached Zip archive.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Almost all resources are commented in both English and French (including the implementation guide) to allow anyone to use it.&lt;BR /&gt;(Only the script itself is written in French with English comments for editable settings).&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I'll be very happy to have your feedback &lt;span class="lia-unicode-emoji" title=":smiling_face_with_smiling_eyes:"&gt;😊&lt;/span&gt;&lt;BR /&gt;Don't hesitate to ask if you have any problems or to suggest improvements.&lt;/P&gt;&lt;P&gt;Have a nice day !&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 01:19:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Automation-script-for-securitization-by-Section-Access-V2/m-p/1751018#M57812</guid>
      <dc:creator>bfournet</dc:creator>
      <dc:date>2024-11-16T01:19:31Z</dc:date>
    </item>
  </channel>
</rss>

