DMXzone Database Connector ASP Support Product Page
Solved
Unable to manage security provider:
Reported 18 Sep 2016 18:03:38
1
has this problem
18 Sep 2016 18:03:38 User posted:
Unable to add/remove manage Security Provider after update. Error at line 416 of dmxSecurityProvider_lib.js
"serverType is not defined"
Replies
Replied 19 Sep 2016 06:57:38
19 Sep 2016 06:57:38 Teodor Kuduschiev replied:
Hello, the security provider is supposed to be added through server connect panel.
Replied 19 Sep 2016 19:25:25
19 Sep 2016 19:25:25 User replied:
Results in the same error.
Have followed "Restrict Access and Redirect Visitors on your Page" instructions exactly.
Have followed "Restrict Access and Redirect Visitors on your Page" instructions exactly.
Replied 21 Sep 2016 06:46:46
21 Sep 2016 06:46:46 Teodor Kuduschiev replied:
Hello,
Please check the following tutorial - www.dmxzone.com/go/32338/filtering-a-database-query-using-the-identity-of-the-logged-in-user/ as it shows the full process and this is the latest tutorial.
After watching it and doing what is displayed, please be a little more detailed explaining when exactly do you see the error you mentioned in your first post.
Please check the following tutorial - www.dmxzone.com/go/32338/filtering-a-database-query-using-the-identity-of-the-logged-in-user/ as it shows the full process and this is the latest tutorial.
After watching it and doing what is displayed, please be a little more detailed explaining when exactly do you see the error you mentioned in your first post.
Replied 21 Sep 2016 18:12:23
21 Sep 2016 18:12:23 User replied:
Unfortunately this tutorial only shows how to protect a query and does not cover protecting access to pages- the only apparent way to protect page access is to insert an empty query and apply protection to the API- which can easily be bypassed by disabling JS.
Replied 21 Sep 2016 18:51:44
21 Sep 2016 18:51:44 Teodor Kuduschiev replied:
If you are referring to security provider enforcer (as your explanation is not clear) please update the security provider and the error will be gone.
And by the way, disabling js won't bypass any of the protection.
And by the way, disabling js won't bypass any of the protection.
Replied 21 Sep 2016 22:28:40
21 Sep 2016 22:28:40 User replied:
I'm assuming its the security provider enforcer, although half of your guides suggest it should be the "Server Connect -> Security Provider" (which only provides the ability to login, but not protect pages), or alternatively, using the Security Provider Executor data bindings which don't appear to be able to achieve either and present the aforementioned error.
Have followed your guides exactly to no avail:
www.dmxzone.com/go/32197/restricting-access-to-pages
Disabling JavaScript does bypass the page protection (tested using Chrome ScriptSafe plugin)- granted, queries are replaced with the api placeholders, but the rest of the "protected" page is perfectly accessible to unauthorised users.
Have followed your guides exactly to no avail:
www.dmxzone.com/go/32197/restricting-access-to-pages
Disabling JavaScript does bypass the page protection (tested using Chrome ScriptSafe plugin)- granted, queries are replaced with the api placeholders, but the rest of the "protected" page is perfectly accessible to unauthorised users.
Replied 22 Sep 2016 07:36:56
22 Sep 2016 07:36:56 Teodor Kuduschiev replied:
The two parts of the extension - security provider and security enforcer are not replacing each other one is an addition to the other. Indeed the video tutorial which i meant to send you was: www.dmxzone.com/go/32197/restricting-access-to-pages
Sorry for the mistake. Please check it and make sure to install the security provider update from yesterday which fixes the error message in the enforcer dialog.
Sorry for the mistake. Please check it and make sure to install the security provider update from yesterday which fixes the error message in the enforcer dialog.