M
Michael Jacobs
Guest
As Mike says, if you have a Windows system available to you it can function as an AppServer who’s only task is to use .NET to manage the authentication process and its storage/handling of account passwords. All of your ABL application modules would call in to that Windows AppServer for login and logout operations. It may be more complex than what you currently do, but it is a recognized model for distributed applications. Mike - I am sure this would work, but have you worked with .NET security libraries in an OE AppServer running on Windows. Curious if there is any examples out there. Mike J. From: Mike Fechner bounce-mikefechner@community.progress.com Reply-To: " TU.OE.Development@community.progress.com " TU.OE.Development@community.progress.com Date: Wednesday, June 25, 2014 at 5:40 AM To: " TU.OE.Development@community.progress.com " TU.OE.Development@community.progress.com Subject: RE: [Technical Users - OE Development] password encryption RE: password encryption Reply by Mike Fechner I'm not a crypto expert at all. But on Windows (GUI, TTY, AppServer) you could use .NET Libraries: stackoverflow.com/.../hash-password-in-c-bcrypt-pbkdf2 or www.shawnmclean.com/.../simplecrypto-net-a-pbkdf2-hashing-wrapper-for-net-framework It should be fairly simple to either build a custom .NET library to do so or translate the code into ABL. Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
Continue reading...