There's no such thing as a stupid question, but they're the easiest to answer.
JoinTour
Login
 
Tag Cloud
access audio avg avg 8 bios blue screen boot bsod computer connection cpu crash css dell desktop dma driver drivers dvd email error excel explorer firefox firefox 3 freeze gimp graphics hard drive hardware hijackthis hjt install internet internet explorer itunes keyboard laptop macro malware monitor motherboard network networking outlook outlook 2003 outlook 2007 outlook express pio problem problems router seo server slow sound sp3 spyware trojan usb video virtumonde virus vista vundo windows windows vista windows xp winxp wireless
Web Design & Development
Search
Search in:
 
Advanced Search
Tech Support Guy Forums > Internet & Networking > Web Design & Development >
Single Sign On


HELLO AND WELCOME! Before you can post your question, you'll have to register -- it's completely free! Click here to join today! We highly recommend that you print a copy of our Guide for New Members. Enjoy!

 
Thread Tools
erocktroll's Avatar
Member with 43 posts.
 
Join Date: Oct 2003
15-Oct-2007, 08:40 AM #1
Single Sign On
**This is a duplicated post -- I posted in the development forum also, as I wasn't really sure where to find an answer....**

Okay, I've been asked to take two systems and create one single sign on application to authenticate to both. I've got one system with php/mysql and the other with Coldfusion/Microsoft SQL. Currently, both are accessed by typing in ip addresses rather then domain names. I'm not sure that I can set up a domain name for them, given the environment.

Currently, each system has it's own login and authenticates to it's own database. I was originally hoping to be able to get this down to just one database, but others involved are fighting this option. So what I was thinking is this...

I'll have a login page which will create a cookie on the system with an expiration date/time, the username, and a randomly created session code. When a user logs in, the session code will be generated by the primary system, and written to a current login table in the primary database. Then, when a user trys to access a secured page, the system will check for the cookie, grab the user name and session code, and check to see if it exists in the database. If it's valid in the db, they are granted access. If not, they are denied and forced to login again. This is okay, I think, as long as they are authenticating to only 1 ip/domain.

Does anyone have any experience with having to create/implement SSO? Any suggestions for improvement in this area? Web development really isn't my area, but none the less, I've been asked to make this work. So I'm giving it a try.....
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are Off
Refbacks are Off

You Are Using:
Server ID
Advertisements do not imply our endorsement of that product or service.
All times are GMT -4. The time now is 12:14 PM.
Copyright © 1996 - 2008 TechGuy, Inc. All rights reserved.
Powered by vBulletin, Copyright © 2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.1.0
Powered by Cermak Technologies, Inc.