CFREGISTRY tag off--- other tags fail!

[neofactor]

For Security... we locked down the CFREGISTRY tag...

But we noticed that some of our sites were giving errors.
The line of code that cause the problem was:

<CFAPPLICATION NAME=&quot;YourAppName&quot; CLIENTMANAGEMENT=&quot;YES&quot; SESSIONMANAGEMENT=&quot;YES&quot;> AND code pertaining to this.

Does Session Management setting use the CFREGISTRY?

The error in MX says: access denied (coldfusion.tagext.genericTagPermission cfregistry)

Any idea? We had to turn CFREGISTRY back on to make the site work, but we want to turn it off in our Enterprise edition of CF MX.

Please shed some light if you can.

 

[csteinhilber]

No... CLIENTMANAGEMENT is what's probably trying to use the registry. Go into CF Administrator and set client variables to be stored in a database, rather than the registry... and I bet that'll solve the problem.



-Carl

 

[neofactor]

ohh ohh ohhh.... yes... stupid me!


For some reason I thought MX would use it's own metatdata to store info.. like IIS went to.

Funny how they dont tell you one tag effects the other.