Hmm, I haven't done this in awhile but IIRC you can:
Turn on Guest access.
Set Automatic login to use the Guest access.
Make sure the IWP layouts use the Classic Theme.
If you use crippled navigation make sure none of the scripts go to a non-classic themed layout. This will break the script.
For your regular users add a check in your startup script for IWP users and if not IWP user then run a login script.
1 of 1 people found this helpful
Here's a blog post that has some details about auto-logging on to an IWP database via a URL
I would recommend against auto-login, as it offers no protection against anyone hijacking that URL and seeing your data. But if you are comfortable, you can assign IWP privledges to the read-only privledge set (or existing priv. set of your choosing), then setup a default IWP user on that priv set and send the username and password via the URL.
I think what I'm hearing is that the IWP user can be indetified??
not PatternCount ( Get ( ApplicationVersion ) ; "web" )
I must disagree.
How is supplying an account and password in the URL better than auto login? Handing over any account info doesn't seem like a good idea to me.
You have the same ability to restrict data access (RLA) using the Guest account as you do with any other Privilege set.
Access may be from a Link on a web page or might be by accessing a web site where only the domain is given.
Either way I suggest you create a redirect landing page so you have control to do whichever method you desire without exposing too much information.
I meant I suggest you don't auto-login via a URL that has the name and password as part of it, not against using the guest account and the built in auto-login in IWP associated with that.
You guys are great! Many THANKS!