eramgarden
Contributor
- Joined
- Mar 8, 2004
- Messages
- 579
I'm at a new job and looking at their app...
Last application I worked with was an internal application to the company that was developed for us by a vendor. They used windows authentication:
There was table with userNames in them..one field was the "windows usename" that the users would type in. So when the app was launched, the windows login was checked against that field. And if I remember correctly, the database had a LOGIN user that was used in the web.config to connect to the database.
Current app I'm looking at is not fully developed yet but in the database, I can see login names. This app is NOT an internal application...it will be sold to potential clients . Would it be better to use "windows authentican" method instead of creating logins..what if a company has 1000 users..then they have to create all these logins.
Any thoughts?
Last application I worked with was an internal application to the company that was developed for us by a vendor. They used windows authentication:
There was table with userNames in them..one field was the "windows usename" that the users would type in. So when the app was launched, the windows login was checked against that field. And if I remember correctly, the database had a LOGIN user that was used in the web.config to connect to the database.
Current app I'm looking at is not fully developed yet but in the database, I can see login names. This app is NOT an internal application...it will be sold to potential clients . Would it be better to use "windows authentican" method instead of creating logins..what if a company has 1000 users..then they have to create all these logins.
Any thoughts?