Working with Coldfusion and .net
We are in the process of wrapping up a project for Redbird Flight Simulations in Austin which presented some unusual challanges for us. Their website is hosted with GoDaddy and sets on a asp/.net platform. Lone Star Media was hired to upgrade their client access section to provide a number of products and services to their members. However, moving from .net to Coldfusion was not an option and they were also not ready to make the switch to <lonestart />. Therefore, we needed to come up with a solution that would enable us to store sessions, authentication and user roles between CF and .net. How did we do it? Cookies 
The top of the website has a loginbug where authenticated users can quickly access their managment page and also logout. The most effecient way to share this information between Coldfusion and .net was by setting a user login cookie on the machine. After all, they both can read the same cookies as long as they are both on the same domain. The login bug simply pulls the data from the cookie to determine the current login state.
The actual client access area is still using CF session authentication as the information is private and secure but by setting a cookie on the client machine we were able to share the authentication state and basic user details between the .cfm pages and .asp pages to ensure a consistant client experience.
Tags: Application Development, coldfusion
You can comment below, or link to this permanent URL from your own site.
