Storing visible signature (jpg) files in AD or Database.
-
I have a meeting tomorrow regarding this subject.We have a case which involves where exactly visible signature files captured and enrolled should be stored, the company has a Windows Active Directory and one option they have is to store it in the user profile attribute jpgPhoto or so.Other would be to store it in a database.One application basically has to query and pick it up and pass it to a signing web service.I feel that storing it in the ad would reduce the "security" related overheads as it is a single point of storage of a user information , rather than replicating it in a database,also the user sensitivity in how secure is his solutions.This may be for max 100 users.The IT admins are gonna give me a tough time.Any good points to store in AD vs Database ?
Caveat Emptor. "Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
-
I have a meeting tomorrow regarding this subject.We have a case which involves where exactly visible signature files captured and enrolled should be stored, the company has a Windows Active Directory and one option they have is to store it in the user profile attribute jpgPhoto or so.Other would be to store it in a database.One application basically has to query and pick it up and pass it to a signing web service.I feel that storing it in the ad would reduce the "security" related overheads as it is a single point of storage of a user information , rather than replicating it in a database,also the user sensitivity in how secure is his solutions.This may be for max 100 users.The IT admins are gonna give me a tough time.Any good points to store in AD vs Database ?
Caveat Emptor. "Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
abmv wrote:
Any good points to store in AD vs Database ?
Ah, lots, I guess.. Let's start the thread with these; Pro AD:
- Fast
- Easy to backup
- No loss due to fragmentation with files that are modified often
- Lots of disk-utilities that can be used on the data
- No added strain to your database-server
Pro DB:
- All data in the same place
- Easy to backup
- No need to give the webservice access to (part of) the file-system
- No added strain to your webserver :)
I are Troll :suss:
-
abmv wrote:
Any good points to store in AD vs Database ?
Ah, lots, I guess.. Let's start the thread with these; Pro AD:
- Fast
- Easy to backup
- No loss due to fragmentation with files that are modified often
- Lots of disk-utilities that can be used on the data
- No added strain to your database-server
Pro DB:
- All data in the same place
- Easy to backup
- No need to give the webservice access to (part of) the file-system
- No added strain to your webserver :)
I are Troll :suss:
-
Lots of disk-utilities that can be used on the data (do u mean ldap querying?)
Caveat Emptor. "Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
