Portal backed by 128-bit Secure connection - the Seal Portal Proje

Finally the Seal Portal now accepts secure connections for preventing your personal information from leaking to a third party person.

The SSL Certificate was registered with the GoDaddy.com Register and snapped into the framework with a breeze. (After a few frustrating moments with my personal certificate. Oh well, I shouldn't be self-certifying anyway!)

Now that the certificate is in place, here is some information on our unique registration process.

What registering really does, behind the scenes.

It connects to a user authorization database. It creates 2 entries. One is the users personal information the second is the users name and password.
This splits the two database making it harder for hackers and third parties to identify your personal information with your email address and password.
ALTHROUGH there is a unique ID number generated that tells the portal that the two are linked.

How your password is used in the system:

It isn't, its only used at the end of a connection to make sure your user name and password match. It is never called upon though out the entire framework of the seal portal.

Your e-mail address defines you but your user ID defines whats yours:

The Seal Portal team decided to distant your e-mail address for as much as possible from user-to-server transactions. Instead one session value is used containing your user ID which the Seal Portal uses for all user specific database transactions. Protecting your email address from potential security risk.

Of course I might of missed a few security protocols and might need reminding of them. So if you have any suggestions feel free to post/comment them here. Enjoy!