RE: iACS share options

[Justin Taylor <JUSTIN@xxxxxxxxxxxxx>]

For people who install iACS locally on every client, how do you control access to features (or do you simply do nothing and accept the risk)?

Thanks



-----Original Message-----
From: Vernon Hamberg [mailto:vhamberg@xxxxxxxxxxxxxxx] 
Sent: Monday, February 17, 2020 9:33 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: iACS share options

Justin

I believe the recommendation is to have each user their own AcsConfig.properties - or one for each functional group of users.

Now how to make that work in your world, I don't know.

Vern

On 2/17/2020 8:20 AM, Justin Taylor wrote:
> How would you control what features are enabled in this scenario?  Presently we use the AcsConfig.properties file in the directory that's shared to the NetServer.
>
> Thanks