Release Notes

Public

9.0.16.4361: Jun 25 2020

New

All platforms - Plastic: We added extra info about Privacy Statement in the Sign-Up screens.

New

All platforms - Cloud2: Soon you will be able to recover deleted repositories!

Right now, if you delete a repository by mistake, you need to contact support to bring it back. Soon, you will have up to two weeks (14 natural days!) to resurrect (or "undelete", as we called it on the GUI) a deleted repository. Once these 14 days pass, the repository data and metadata will get removed forever.

New

All platforms - Server: We implemented a token renewal system!

There's still work to do, but we are getting closer to renewing the full token system.

We actually implemented this because the new tokens in cloud2 expired during long replicas, which was not good.

New

All platforms - Plastic: the "Pending changes" view now does fewer calls to the server!

The refresh of the "Pending changes" view now performs half of the original number of calls to the server.

This decrease in calls improves the refresh performance over a slow network. Besides that, it reduces the server load. As a result, the server is able to handle more user requests with the same resources.

New

All platforms - Client and Server: We added experimental support for UDT and Secured UDT for Plastic Protocol!

UDT was historically supported only on Windows servers. We changed that a few releases ago, but still it only worked with the about-to-be-deprecated Remoting protocol, which means it was not possible to use it with .NET Core builds. Also, it was not secured.

Now this changes and you can both configure a regular server and a .net core one to support UDT. Our preference is to run it on .net core buids.

== How to configure remoting.conf ==

Required only for .net servers: add a new channel to the xml in remoting.conf

                <channel type="Codice.Channels.UdtChannel,plasticpipe" port="1024" name="udt1024">
                    <serverProviders>
                        <formatter type = "PlasticPipe.Remoting.PlasticBinaryServerFormatterSinkProvider, plasticpipe" typeFilterLevel="Full" Compression="sinklevel" SerializationObjectsAtSink="true" />
                        <provider type = "Codice.CM.Server.ExceptionTracerSinkProvider, servercommon" />
                    </serverProviders>
                    <clientProviders>
                        <provider type="PlasticPipe.Remoting.ClientSinkProvider, plasticpipe" />
                        <formatter ref="binary" />
                    </clientProviders>
                </channel>

== How to configure for .net core servers ==

Modify your network.conf to add this:

[
  {
    "security": "ssl",
    "type": "udt",
    "port": 7751,
  },
]

Where security can also be "none"

== How to use it from the client ==

# Regular connections:
> cm.exe repo list udt://192.168.221.142:7751

# Secured connections:
cm.exe repo list sudt://192.168.221.142:7751

Remark: this is still pretty much experimental!

New

Windows - Plastic: We disabled the controls on the Pending Changes view when refreshing its contents!

Clicking on "Checkin", "Undo changes" or the refresh button while the Pending changes view is being refreshed does nothing. We now disable those controls during the refresh, to avoid confusion.

Bug

All platforms - Client: The "Token expired" showed up again in LDAP servers and Cloud.

We fixed an issue that we think only happened on sync views between local/on-premises server and Cloud:

* You tried to recalculate a sync view

* But the token to cloud expired

* But you ran a command recently from outside the GUI with another GUI or command line

* The initial GUI throws token expired and it takes its time to recover

We hopefully fixed it.

The issue was because the profiles were not reloading tokens, while the underlying conn mechanism reloaded tokens.conf since a different app had changed it. Little bit weird but we saw it a few times.