In JP's eZine on page 16, under:
> VST SCANNING OPTIMIZATIONS AND ENHANCEMENTS
it states that
> Unauthorized plug-ins no longer appear in SONAR’s user interface.
What makes a plug-in authorized or non-authorized?

Authorization is as defined by the plugin vendor. The article was referring to plugins like Waves plugins that supply a single dll package that contains several plugins. As you authorize them they will appear in SONAR. Unlicensed plugins will be removed from the scanned plugin list and will not show up in SONAR.

Oh, that kind of authorized.
 
Wow, there must be almost as many authorization methods as there are vendors. JP covers them all? Impressive!

Noel Borthwick [Cakewalk]As you authorize them they will appear in SONAR.

Well, then how about if a plugin requires authorization within a DAW?

Soundwise

Noel Borthwick [Cakewalk]As you authorize them they will appear in SONAR.

Well, then how about if a plugin requires authorization within a DAW?

indeed, how else does one authorise? some plugins have a separate little app to do it, others a standalone version of the plugin, but the majority needs loading in a host to complete authorisation... and those "demo mode until authorised" plugs - much like sonar's new licensing/authorisation - where do they stand?

I just installed a couple of synths I picked up cheap from Linplug. Platinum (JP) recognizes the plugin pre-authorization as it always did, and allowed me to enter the serial numbers for them within SONAR. Presumably demos are still 'authorized' to SONAR.

I think the wording of that might be confusing - it doesn't affect demos. The changes are only indirectly related to authorization. I'll try and explain.
Basically VST2 and VST3 dll's can contain multiple modules. e.g a single Waves DLL can contain hundreds of plugins.
The individual plugins in the dll will only work if they are authorized by the plugin vendor. In the case of Waves you do this via Waves License manager (WLM). Licences can be moved between ILok's or different computers so if you have a set of plugins authorized and move the license they now become unauthorized on that PC.
 
With the new changes SONAR will automatically rescan the dll and detect that it contains fewer plugins and remove all the old plugins from the VST cache so you won't see them anymore. That is all. Prior to this, under some conditions the old plugins could get left behind, leading to confusion. ie. they would appear in menus but if you tried to insert them they would fail. Also there were cases when you authorized a new set of plugins from the dll without updating the dll itself, SONAR wouldn't pick them up since it thought the package was up to date. This is why sometimes people had to force a rescan to see these plugins. Hope this helps explain it.

Noel Borthwick [Cakewalk]
 
With the new changes SONAR will automatically rescan the dll and detect that it contains fewer plugins and remove all the old plugins from the VST cache so you won't see them anymore. That is all. Prior to this, under some conditions the old plugins could get left behind, leading to confusion. ie. they would appear in menus but if you tried to insert them they would fail. Also there were cases when you authorized a new set of plugins from the dll without updating the dll itself, SONAR wouldn't pick them up since it thought the package was up to date. This is why sometimes people had to force a rescan to see these plugins. Hope this helps explain it.

That explains that Sonar is smarter than some users. What does "old plugins" mean? How does Sonar detect that dll with a set of plugins is up to date or not? If there is a newer version of a plugin available will Sonar prevent using an older version?