Our Script Packaging series continues with an introduction to the Script Packager Credentials feature.
These days modern security mechanisms frequently work without passwords or user IDs. Instead, biometrics, access cards, trusted connections, etc., are usually far better mechanisms for authentication. But some of them require additional hardware or, at the very least, software infrastructure. You may not have the luxury of shiny new security protocols and hardware when you create scripts to access legacy servers, databases, or storage devices. As a matter of fact, in some instances, it may be decades before all the old stuff gets replaced.
This is where our Script Packager Credentials feature comes in handy.
In the past, you may have occasionally been compelled to hard-code credentials into scripts. We know; we have seen some examples. But, to make it clear, you should not do that. At the very least, use an encrypted file.
By using the credentials feature in the SAPIEN Script Packager, you can add credentials to your packaged executable’s resource and load them at runtime. They are, of course, stored encrypted.
This mechanism is not 100% secure, but it is far better than having script block logging add your user ID and password to the Windows log file.
For a more detailed discussion on this topic and this feature, please see Still using Credentials in your Code?
- Still using Credentials in your Code?
- Script Packaging Step-by-Step: Choosing a Script Engine
- Script Packaging Step-by-Step: Output Settings
- Script Packaging Step-by-Step: Adding icons to your application
- Script Packaging Step-by-Step: Adding Restrictions
- Script Packaging Step-by-Step: Version Information
- Script Packaging Step-by-Step: Custom Build Commands
Any comments or suggestions? Please feel free to comment below or in our support forums.