web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Restrict Access to Run...
Microsoft Dynamics GP (Archived)

Restrict Access to Run Integration

(0) ShareShare
ReportReport
Posted on by mebenz 3,815

I see where I can disable access to Integration Manager and Table Import.  I also see where I can restrict access to the Integration Site Enabler.  None of our users have access to these, yet they have access to "Run Integration."  This was an issue on Dynamics 10 and is still the same on Dynamics 2013. 

How do I restrict a user from accessing Run Integration other than removing INtegration Manager from the set file (we are on citrix so it's not like we can just not install Integration Manager).

*This post is locked for comments

I have the same question (0)
  • L Vail Profile Picture
    L Vail 65,271 on at

    You will need to use VB Script to require a password before the integration can be run.

    Kind regards,

    Leslie

  • mebenz Profile Picture
    mebenz 3,815 on at

    I'm confused.  The "Run Integration" is a menu item. Why can it not be restricted/allowed for certain users?  We have over 25 integrations.  I can't really be expected to have to password protect them all and maintain all these passwords.  

  • Community Member Profile Picture
    Community Member on at

    I think this will work on Citrix, based on installed I have done in the past on Citrix.  

    The location of the integration database is stored by the user in Citrix (not sure if in registry or in user specific files).   Anyway, log in via Citrix as the user that you want to deny the ability to run integrtions to.  

    Pull up integration manager and go to Tools>Create Database.   Create a blank IM database.   Then, Tools>Options and point to the newly created IM Database which is empty.  

    So, I believe what you will wind up with is, that users you want to allow to run integrations will be pointed at the real IM database and others you don't will not see any integrations to run.  

    Test this approach and see if it works.  No promises.  

    Warren

  • L Vail Profile Picture
    L Vail 65,271 on at

    Hi Mebenz,

    We'll come up with something for you :)

    Do you want some users to have the ability to run certain integrations, but not all integrations, or is it an all or nothing situation?

    Leslie

  • mebenz Profile Picture
    mebenz 3,815 on at

    We did use separate set files for users to get around this users but didn't want to do this with the new version.  We want to be able to restrict the app completely for users and those with access could runwhichever ones allowed them to run (ie Dynamics security allows or resrticts the windows as we don't use eConnect).

  • mebenz Profile Picture
    mebenz 3,815 on at

    We modified the integration manager ini file to point to the mdb file so we didn't have to do the location for every user.  Plus we have 4 citrix servers in a farm so we'd have to repeat that if they happened to log onto another server.  

  • Community Member Profile Picture
    Community Member on at

    Did you ever get an answer on simply hiding or graying out the "Run Integration" option in the drop menu?  Looking to do the same thing for Run and Record Macro options.

  • Suggested answer
    L Vail Profile Picture
    L Vail 65,271 on at

    Hi,

    Security will not prohibit this. I realize it's a menu item and you ought to be able to use security, but you cannot. You can remove the IM dictionary from the workstation (and change its Dynamics.set file), but the menu item cannot be restricted using Dynamics security. The way around it, is to either require a password using VB script in the integration itself or not allow access to the access database .mdb file (or whatever it's being called now) such that the user wouldn't be allowed to open it. You can also remove the settings that indicate the location of the 'run integration' executable (IMExecPath=) from the Dex.ini file.

    Kind regards,

    Leslie

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans