I'm not sure if these are options for what we're trying to do. My understading is that if we use OpenID or Live for one site then we need to use it for both sites. That's not an option for us.
Here's our situation.
Our client has an existing site (non-DNN) where users' usernames/logon/profile information are stored. THe site that we'll be building is to supplement that original site with some new functionality.
We're envisioning something where users will click on link on this existing site that will post their username and a token of some sort to the DNN site which, if it's the first time they've come to the site, will auto-enroll them and automatically enter whatever user data we're provided. We would not prompt the user to enter anything.
The next time they visit (by clicking on the same link on the other site) we recognize that they are a returning user and simply validate them and let them in.
The SeeleyWare Auto-Logon module could handle the validation but wouldn't handle the auto-enroll process.
An option is for us to have a nightly process that would load new users into our system after the parent site enrolls a new user and then use the SeeleyWare module for logins.
Anyone have any thoughts or suggestions?