Some of these processes may be deemed to be unnecessary or too unsecure to run on a production DoD.ĬoldFusion must require a username and password for access by each authorized user access. To reduce.ĬoldFusion must disable Flash Remoting support.Īpplication servers provide a myriad of differing processes, features and functionalities. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. Some of these processes may be deemed to be unnecessary or too unsecure to run on a production DoD.ĬoldFusion must limit the SQL commands available.ĭoS is a condition when a resource is not available for legitimate users. In this case, it’s just unfortunate timing that Big Sur was released the same week as CF2021 itself.Findings (MAC III - Administrative Sensitive) Finding IDĬoldFusion must have Remote Development Services (RDS) disabled.Īpplication servers provide a myriad of differing processes, features, and functionalities. And sometimes it’s InstallAnywhere that is not updated until the new os comes out, and then Adobe has to build and test a new installer based on that, which adds to the delay.
These challenges always happen with any new OS and to users who are compelled to move to it quickly or who buy new machines with it–and not just with CF, of course.įinally, in such cases, it’s technically not CF or CFB that “don’t work”, but rather the issue is usually with installanywhere software that underlies the cf installers. But they may well opt to get only that new version to work with Big Sur, and not CFB2018. No telling if that’s weeks or months out from now. As you may know, Adobe has announced plans to move from an ECLIPSE base to a VSCode base, and they’d indicated that would not come out with cf2021 itself (released in Nov) but after it. Often they only do such a new installer (for a new OS) for the latest CF version, even when it’s so brand new like CF2021.Īs for CFBuilder, it’s harder to predict.
If past patterns hold, it seems reasonable to expect a new installer for the new OS when an update of cf2021 comes out, though there’s no guarantee it would be with the first update.Īs for CF2018, I’m not so sure we should expect a new installer, let alone for cf2016 (whose support and updates end in Feb). But I realize you’re asking this as much just to remind them that folks are waiting. (See below for why it should.)Īs for when we’ll get a new CF installer for Big Sur, we don’t tend to hear dates (or even estimates) from Adobe in advance, as you’ll know from your years with CF. It would be great to hear if Big Sur folks might confirm if that works for them now. See the docs or another post here for more on that.
Larry, I realize you and others will likely prefer to hear from Adobe, but until they may respond, I have some thoughts that may be helpful.įirst, here’s some possible good news: while the GUI or console installer won’t work with Big Sur yet, I suspect the new zip installer for cf2021 would work fine. That forum post does also list and links to resources on the many new features. Perhaps we’ll see a similar post like that from them here as a blog post on the portal, but until then I’m glad to be able to point this out. Introducing Adobe ColdFusion (2021 release) Update: I found after writing the above that Adobe had posted the news in a forum post insted: Go check out the post and get the new version. I count nearly 60 of them, and as always they range from the features great to small, any of which may delight you. The many new and improved features in CF2021 Until then (and even after), check out a blog post I did just hours before the release where I list the many, many new features, as I had gathered them from the prerelease (which at the time was open to the public): I’m sure we’ll see posts from Adobe in due time. I don’t see that Adobe has offered a blog post here yet (though a new banner is showing it), so let me be the first to announce that ColdFusion 2021 has been released today, and yep, the name is indeed CF2021.