Jonas, Well, you can disable older protocols. But, that is not possible for you because you want to allow some tools but not others from the older protocol.
You can disable access from given client types. But, that is not possible as you do want that client type to access but just version restricted. (you can also specify timing for the restriction and users but again, not useful for your case as you want the user and the time and the client type just not specific older versions of this client.) NOTE: You could use this setting to disable being able to run the old Remedy Admin tool as that is a different client type than Dev Studio. So, you could protect from pre 7.5 administration using this feature. The feature is the Disable-Client-Operation option that can be set in ar.conf/ar.cfg and is documented in the AR System Configuration Guide pgs 365-366. You can restrict the Admin to ONLY running in overlay mode. That would prevent that Administrator (you can configure this for each Admin so you can have one/some/all Admins given this restriction if desired) from running in base mode and making any changes. See AR System Configuration Guide page 83 (in version 7.6.04 as this feature was added in that release) about Access Restrictions for Administrators. This doesn't prevent the 7.5 Dev Studio, but it DOES make sure that regardless of version, the user cannot make modifications to ANYTHING in base mode as they only have rights to change things in overlay mode. Again, not everything, but a protection and that protection may be useful regardless of the version of dev studio being run. So, there are a lot of ways to restrict access, but not the exact combination you are asking about. The only other option is to essentially run with API logging turned on and see if there are any "entry" operations performed (other than GetListEntry or GetListEntryWithFields which have no workflow that fires on them) and put workflow that checks client type and version and returns error messages when it sees Dev Studio of an older version. This may not prevent the user from connecting, but it may cause them to have to consciously see and deal with errors that could be repeated warnings about a version mismatch (and combined with restricting them to overlay mode may give enough pain to force them to move forward). I don't know if there are or what specific entry operations dev studio may or may not make -- but you could turn on logging to see if it does any. This is the best we can offer for today. I hope this at least gives one more idea about the forcing the Admin to work in overlay mode (which by the way may block the 7.5 Dev Studio by itself as it will be connecting in Base mode rather than Overlay mode and it cannot change the mode it is connecting in and the Administrator doesn't have rights to work in that mode would essentially turn that version of Dev Studio into one that either cannot connect or connects only in Read only mode for those users.) Doug Mueller -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Jonas Stumph Stevnsvig Sent: Wednesday, February 22, 2012 9:42 AM To: [email protected] Subject: Disalowing 7.5 developer tool on a 7.6.04 system Hi listers I have a little question which bothers me, and I hope you can give me some insight. The background: We are about to go live with a new 7.6.04 sp2 environment. We have several consultants, not all of which are familiar with overlays. We almost had a catastrophe today with a person logging onto the new server with a 7.5 dev studio. He did not get any warnings about base/overlay mode, and almost wrecked a form by deleting fields from the wrong place. I am aware of the lowest api level, but our ITSM installation is still at 7.6.00 so there are some old plugins at api level 7.5 (or thereabout). The Question: How do I disallow dev studio connections < 7.6.04 without disallowing the plugins? Any suggestions? Best regards Jonas _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
