Attached is a document with specifics on how to use the iMIS15 MembershipWebService to login a user from a third party site.
Please comment with any errors, omissions or additions you may have.
80% of the development of this process was done with the help of Eric Means.
Thanks,
Mike
| Attachment | Size |
|---|---|
| Technical Process Description Unified Login.doc | 283 KB |
This allows you to authenticate against the db - not necessarily update/read from it.
There are many potential reasons to do this, I would say that every large web implementation requires coordination of authentication across multiple sites.
Clients that have 2, 3 or more sites try when possible to have the user authenitcate only once. Especially now that we have ASP.NET code, that authentication pretty much needs to be iMIS.
This should count as a public user in the licensing scheme, because the login does not occur except through the iMIS public view.
Mike
An additional need to to be able to determine the logged in users ID from the MembershipWebService.
I tried doing a cfinvoke in ColdFusion, using code like this below (after I had logged in). It said that the variable "results" was undefined.
Shouldn't it just return the user name in results.
"#results#"
alert('MembershipWebservice Error \(ValidateUser\) #cfcatch.message#');
history.go (-1);
Hi Mike, this doc has been a great help but I have a couple questions for you.
In our scenario, we have 3 physical servers. A CF web server, an iMIS public server and an iMIS application server. These are all production servers, they don't have a test environment at this time as they're a pretty small shop.
In this scenario, I think that we need to use the in the web.config for both the public and the app server, so that they apply the same encryption to the cookie strings on both ends.
First question - Is this correct?
Second Question - If we apply the machine key does it take effect immediately or do we have to restart anything, and is it safe to apply a machine key to a running production server?
Thanks!
How does this membership service work. The MembershipWebService.asmx referres to a cs file that does not exist, and it references other commands that are not listed in any of the files in the site. Does this service act like the Public Site Logon, when the attemp fails a certain number of times the account is locked. Is there any more documentation on this service other than the http://www.xyz.com/iMIS15/ASICOMMON/Services/Membership/MembershipWebSer... URL? We have a 3rd party site we created and would like to use this service but need to know more about it. Thanks.
Christopher W. Marsch, Database Administrator
MEMA
10 Laboratory Dr
Research Triangle Park, NC 27709
(919) 406-8813
Logins
I am not sure that I understand the purpose of this approach. It seems to be to allow a web site user to be authenticated against the iMIS database without having an ASI public view license. Is this correct?