Typically, you buy an SSL certificate for a server from a SSL vendor. However, some companies may decide that they want to issue their own SSL certificates. Often this is because the domain is only used internally, and most vendors don’t easily allow (if at all) the signing of server certificates for non-public domains. Additionally, issuing your own certificates can remove complications caused by the certificate verification process used by most vendors, and there are no fees needed for each certificate.
Solving an Old Problem
When you consider how to keep information safe, you might first imagine a team of hackers in a dank basement typing and clicking their way into your bank account.
It’s FileMaker Developer Conference time, with 8 Beez in San Antonio for DevCon. We’re studying new development techniques from FileMaker Inc. and our industry peers, sharing a few methods of our own and even riding a few mechanical bulls at a real live cattle ranch!
Applets now are required to contain additional information in their .jnlp files to document the files used, either external or local. But if you are working with older code, such as the FileMaker 11 Server Admin Console, the required manifest information is missing and your applet will halt with an exception like this:
java.lang.SecurityException: Missing required Permissions manifest attribute in main jar: http://localhost:16000/admin-client-lib/admin-console-client.jar at com.sun.deploy.security.DeployManifestChecker.verifyMainJar(Unknown Source) at com.sun.deploy.security.DeployManifestChecker.verifyMainJar(Unknown Source) at com.sun.javaws.Launcher.doLaunchApp(Unknown Source) at com.sun.javaws.Launcher.run(Unknown Source) at java.lang.Thread.run(Thread.java:744)
I needed to configure a FileMaker Server (FMS) that would be an isolated system and accessible via the Internet.
Besides other precautions, like locking it down on the firewall as much as possible, changing the default SSH port, etc., I wanted to give the system some ability to defend itself against malicious access. FMS will prevent this to some extent, largely due to how the FMS Admin Console and the FileMaker client are designed.
I wanted to code sign a runtime to avoid issues with users who had the higher security level set on their 10.8 based systems. Although lowering these permissions or holding down the control key when the app is launched will all help with this issue, code signing seems a reasonable and desirable, and removed the support issue.
FileMaker, Inc. introduced the next generation of their database platform today with the release of FileMaker 12. This is a major upgrade to every part of the FileMaker product line. There are new versions of FileMaker Pro, FileMaker Pro Advanced, FileMaker Server, FileMaker Server Advanced, and FileMaker Go – which is now free for iPhone and iPad.
Here’s an interesting interface challenge we recently faced: A client needed to place text fields on a layout and fluidly choose which fields would be editable or read-only—the same field might exist in both editable and read-only state on the same layout.
Now, here’s the challenging bit: Each read-only field must have all the same capabilities of its editable cousins—users must be able to scroll, select, and copy text, and the field control must display all rich text formatting entered.