Has anyone had any experience wrapping a custom Single Sign On solution around iMIS web? We'd like to leverage our existing solution and pass the credentials over to iMIS.
Thanks,
Mark
Single Sign On Solution with iMIS Web
Mark, I have also done
On August 31st, 2010 james_schwartz says:
Mark,
I have also done something similar whereby the user logs into another system - which generates a token - and then when they browse to the iMIS website, we read the token and user ID and if the token is valid for that user ID, we impersonate that user ID by logging them into iMIS automatically.
The password does not get passed over the wire at all - it's all based on the token.
Feel free to email me if you would like any more details on this solution - james.schwartz@imason.com
Cheers,
James
Single Sign On Solution with iMIS Web
On August 31st, 2010 melliott9 says:
Thanks for the responses and the info. Sounds very promising, yes we would be interested in learning more about how you did that.
Thanks,
Mark
Single Sign On
On September 1st, 2010 ShirleyMartin says:
I'd like more details about your Single Signon solution.
We have a custom web application that we would like to authenticate through iMIS. The user would log into the iMIS public site and we'd send a token to the custom site saying they're a valid user. I'd also like to send the user's name and email address.
Is this this possible?
Other solutions
On September 1st, 2010 rrichter says:
I know many of the AiSP's have been replying here and some have not. There are already a lot of bridges built to products like GoToWebinar, Blue Sky, SalesForce.Com, Ektron, Drupal, and others.
The options that I see are to
1. Build something yourself using the .NET iMIS Business Objects
2. Build something using the iMIS SOA Web Services
3. Build something from one of the AiSP's like the single sign on web services from us (other AiSP's have them too). http://www.atsol.org/demo/webservices
4. Find an already built solution from one of the AiSP's.
Those are some of the most common solutions. Our clients usually use 3 and 4 and hand over the integration to their AiSP's.
The achievable goal is to use realtime integration using the webservices. Some third party vendors will say, just send me a file of usernames and passwords. That should only be used as a last case resort and should be a requirment and predictor of the third party's technical ability. In todays world with the solutions that iMIS provides real time integration is achievable and relatively inexpensive.
Thanks,
Randy Richter (rrichter@atsol.org)
SSO
On September 1st, 2010 lmbrown says:
Hi Shirley,
Send me your email address and I will be happy to send you some information regarding the SSO that we have. We have also designed it to allow additional fields to be passed through such as email
Thanks
Lisa
SSO
On October 4th, 2010 jstemper says:
We went down the route of using IBOs to authenticate against iMIS and retrieve a token on succesful authentication. The token is then passed along to our externally hosted web sites which then use it to validate the users. We did wrap the web services in a layer of our own to add a little security and some additional logging for own administrative purposes.
This solution is in place to allow 4 different ASP hosted websites to all look and work smoothly together.
John
SSO
Hi Mark,
We have a single sign on solution that allows a member to log into the iMIS public view and then pass to basically any type of 3rd party content management system. Email me at lbrown@ibconcepts.com if you would like some more information
Lisa