November 10, 201015 yr Newbies Hopefully there’s a simple answer to this… I’ve only been using SuperContainer for a few months, and I’ve got our solution working pretty well, but I’m having problems with the security features. (Everything works fine if security isn’t turned on, and I’m running 2.77 on the server and as a plugin) For the following examples, assume I’ve activated the security on the server, with the username ‘name’ and the password ‘pw’. I’ve got a script that sets the base URL on startup, trying to include the username and password as follows: Set Variable [$result; Value: SCSetBaseURL ("http://name:[email protected]:8020/SuperContainer/Files") OR Set Variable [$result; Value: SCSetBaseURL( "http://server.org:8020/SuperContainer/Files"; "name" ; "pw") Neither generates an error, but they also doesn’t seem to help me (i.e. – with security activated, SuperContainer portals return errors, and no plugin functions work) So, to get around this, for all my portals I’ve included the username and password in the URL, adding the following to the very end: & "&username=name&password=pw" This works for all the portals. But I can’t figure out a way to include the username and password when using functions in scripts. For instance, I’ve tried the following function in a script: SCGetInfo( "/Photos/" & Photos::Photo_ID & "?username=name&password=pw" ) This doesn’t work. In the SuperContainer server log, it acknowledges the user name, but complains that the password is wrong (even though it’s correct). I’ve tried creating a URL with the same formatting and it works fine in a browser, so I know the username and password are valid, but I can’t figure out how to get the function to work in a script. I’m sure I’m missing something obvious, but the online documentation is a little sparse for the security features. Any help or examples would be appreciated. If there’s a way to log in for the entire session, that would be great, but I don’t mind coding all my scripts with the security info if necessary. I'm just not sure of the correct syntax. Thanks so much! -Neil Edited November 10, 201015 yr by Guest
November 10, 201015 yr There are a few different places that supercontainer can be used. The first is in Web Viewers, which are what display the web content and the SuperContainer applet. You need to pass the username and password as URL parameters in this case, as many browsers do not support the username:[email protected] url style. The second implementation of SueprConainer in your database is through the plugin. The plugin is entirely independent of the web viewers and any URLs that you use in the web viewer. To use any of the plugin functions you must first call SCSetBaseURL, in which you pass the username and password as function parameters, which you do in your example above. The SCSetBaseURL function is the only place where you can specify the username and password, and once it is done here you do not need to do it again in your database (other than in web viewers, which are independent of the plugin). You should not add URL parameters to your path variables for your plugin functions, such as you are doing in the SCGetInfo function above.
November 10, 201015 yr Author Newbies Hi David— Thanks so much for the quick reply. The distinction between Web Viewers and the plug-in makes perfect sense now that you point it out. Seems like I’ve got the names and passwords in the right place and as far as I can tell, it’s all working now! -Neil
Create an account or sign in to comment