Databases Reference
In-Depth Information
We used a hidden script tab to create our section access. When using regular
script, any user with privileges to view the script has full access to either the user
credentials in plain text (when using an inline table), or to the location of the access
files (when using an external table file). By using a hidden script, we can limit who
will be able to see the section access script, adding an extra layer of security.
Another thing that you may have noticed is that all field names and field data are
written in uppercase. While technically this is not necessary for data loaded from an
inline table, any data loaded in section access from an external source must always
be in uppercase. For the sake of consistency, it is a good idea to always load all data
in uppercase in the section access area.
Now that we've seen how a basic section access example is set up, let's see if it works
by following these steps:
1.
Save the document by selecting
File | Save Entire Document
in the menu.
2.
Click on
OK
to close the
Edit Script
dialog.
3.
Close QlikView Desktop by selecting
File | Exit
in the menu.
4.
Reopen QlikView and the
Airline Operations SA.qvw
file.
5.
In the
User Identification
input box, enter
admin
.
6.
In the
Password
input box, enter
admin123
.
If everything was set up ok, you should now be back in the document. Feel free
to repeat these steps and enter wrong usernames and passwords to verify that
QlikView will deny access to the document.
QlikView will only verify your user credentials once during
each session. You can verify this by closing the document and
reopening it, without exiting QlikView Desktop. QlikView will
not ask for your username and password the second time. Only
when you completely close and reopen QlikView Desktop will
you be asked for your credentials again. This is important to
remember when changing and testing section access.
