Here's what I posted on FMForums before. This is the extent of the info I'll provide - it's up to you to figure it out from here:
Force-authenticate with guest:
<http://www.yourdomain.com/fmi/iwp/cgi?acct=guest&login=Login&-authdb>
or a user:
<http://www.yourdomain.com/fmi/iwp/cgi?acct=account&name=username&password=password&login=Login&-authdb>
then, modify your IWP home page to detect for
www.yourdomain.com(using JavaScript) and rewrite to the direct address for your
database:
<http://www.yourdomain.com/fmi/iwp/cgi?-db=databasename&-startsession>
You can use separate secondary domains (db1.yourdomain.com,
db2.yourdomain.com...) to detect against if you need to specify
different databases to bounce to.
However, if the forced authentication is used again though, then it
won't normally clear the session first until the browser is
restarted, and instead of properly authenticating the main domain is
just gone to instead.
So, if you use the secondary domain tip above, you can just make an
index.html page that clears the session cookie, then re-visits the
forced authentication URL. Here's how I did it in Lasso:
[cookie_set: 'http-session'='', -expires='-1', -path='/fmi/iwp']
<html><head>
<meta http-equiv="refresh"
content="0;URL=http://www.yourdomain.com/fmi/iwp/cgi?acct=guest&login=Login&-authdb">
</head><body></body></html>
Got it? =)
Of course, we set this all up for our clients without them having to deal with it.
- John