{"id":7432,"date":"2016-06-24T09:52:40","date_gmt":"2016-06-24T13:52:40","guid":{"rendered":"https:\/\/blogs.mathworks.com\/pick\/?p=7432"},"modified":"2016-06-24T09:53:41","modified_gmt":"2016-06-24T13:53:41","slug":"get-authentication","status":"publish","type":"post","link":"https:\/\/blogs.mathworks.com\/pick\/2016\/06\/24\/get-authentication\/","title":{"rendered":"Get Authentication"},"content":{"rendered":"
\r\n \r\n

Sean<\/a>'s pick this week is GetAuthentication<\/a> by Stefan<\/a>.\r\n <\/p>\r\n <\/introduction>\r\n

I was recently asked about a simple way to password protect an executable compiled with MATLAB Compiler<\/a>. The customer's goal was that this would be on a shared machine and only authorized users would be able to use the executable.\r\n <\/p>\r\n

It occurred to me that I frequently use a MATLAB-based password box every time I upload a file to our FTP or SFTP site to\r\n share with customers. Digging into the code there, I discovered this file and was excited to see it publicly available on\r\n the File Exchange.\r\n <\/p>\r\n

To use it to protect your executable, simply call it in a wrapper function to decide whether to open the main executable or\r\n quit. Here's a simple example that gives access to my four dogs to see a picture of themselves.\r\n <\/p>

\r\nfunction<\/span> authenticateApp()\r\n% This function authenticates a username and password before opening an<\/span>\r\n% application.<\/span>\r\n\r\n    % Username and password for each of my dogs<\/span>\r\n    unames = {'Zoey'<\/span>, 'Mya'<\/span>, 'Lexi'<\/span>, 'Lilly'<\/span>};\r\n    passwords  = {'MilkB0ne'<\/span>, 'Dent@Stix'<\/span>, 'Pupp3roni'<\/span>, 's0ck$'<\/span>};\r\n\r\n    % Try three times<\/span>\r\n    for<\/span> ii = 1:3\r\n        % Get authentication<\/span>\r\n        [user, pass] = GetAuthentication();\r\n        \r\n        % Does a username match?<\/span>\r\n        useridx = ismember(unames,user);\r\n        if<\/span> nnz(useridx)\r\n            % If yes, does the password match for that user?<\/span>\r\n            if<\/span> isequal(useridx, ismember(passwords,pass))\r\n                \r\n                % Open application here:<\/span>\r\n                imshow('fourdogs.jpg'<\/span>)\r\n                \r\n                break<\/span>\r\n            end<\/span>\r\n        end<\/span>\r\n    end<\/span>            \r\nend<\/span>\r\n<\/pre>
Calling it:<\/p>
authenticateApp<\/pre>
 <\/p>\r\n   
 <\/p>\r\n   
 <\/p>\r\n   
Compiling<\/a><\/h3>\r\n   
Now if you want to compile this, make the authentication wrapper the main function and your app will have this protection\r\n      around it.\r\n   <\/p>\r\n   
 <\/p>\r\n   
Suggestion<\/a><\/h3>\r\n   
My only suggestion would be for GetAuthentication<\/tt> to pass back a third output argument about whether the user hit the cancel button.  Right now, if cancel is hit, it just\r\n      returns empty for password and username.  This is ambiguous to hitting okay with empty password and username which is a challenge\r\n      to handle if you want to use it in a loop like I did.\r\n   <\/p>\r\n   
Comments<\/a><\/h3>\r\n   
Give it a try and let us know what you think here<\/a> or leave a comment<\/a> for Stefan.\r\n   <\/p>