Let's get the positive things out of the way first. RESTlets are great from the point of view of they're a web standard. Yay!
Now for the bad news.
RESTlets require a full set of NetSuite credentials to be forwarded to NetSuite in plain text with every request. "But HTTPS!" I hear the masses cry; that's all well and good until you consider the need to store those credentials somewhere (again, in plain text) to be sent with each of those requests. :h_a_w:
I'm not altogether comfortable with putting a full set of NetSuite login credentials into a database, or flat file, or some other means of storage that has to be accessible (by necessity) by my applications that I want to integrate using REST.
Consider that the username and password could grant access to multiple accounts (that may be entirely unrelated with the account containing the RESTlets in question) and that the same credentials used to authenticate with limited-impact RESTlets can be used to log into the full NetSuite application.
My question to the community (and by extension to NetSuite) is how do we manage that risk?
Were the system design in my hands I'd have a set of credentials that can only be used to authenticate REST requests (meaning no UI access with those credentials) and that could only be used with a single NetSuite account, regardless of how many accounts the user in question has been granted access to. As it is now, we're basically handing out the keys to the kingdom in the event an application utilising RESTlets is compromised or flawed in any way. I'd rather not roll my own API key system using publically-exposed Suitelets, but it seems like that might be the safest option.
Thoughts?