I have developed a set of add-ins. Our organization has different branches and divisions. I would like to share the add-ins with a group of people and some individuals maybe. Is there way to insert some kind of password for each user so they will enter the password to use the add-in
Hi,
Look at the ArcGIS Pro samples:
https://github.com/Esri/arcgis-pro-sdk-community-samples/tree/master/Framework/Licensing
You can build extension and authorize it by password. Add-ins could be enabled/disable by conditions and extension.
If your organization is running Active Directory, you might consider setting up a group for each AddIn. You could then override the Module Initialize method so that it checks to see if the user is a member of respective group, and set a member variable _isAuthorized accordingly.
The components in the module could then check to see if module.IsAuthorized before enabling its functionality.
Hi @KirkKuykendall1 and @GKmieliauskas ,
I think I will need to use both of the solutions you guys offered. I will come back with results. Thanks for the answers.
Hi @Amadeus111 ,
If your organization is using windows active directory, you can set windows ACL at folder permission level.
And then configure these individual folder in the add-in folder registry.
Recently, I have done enterprise roll out with cloud offering with this way and it is simple and easy to manage with windows user group. User don't need to login to Add-in and if they don't have permission, they just simply cannot see the add-in.
@GKmieliauskas Thanks for the solution! I was able to apply the sample code to my add-in but now facing two problems. One, I need to provide unique product id for each user and that can not be used more than once. Two, I would like to implement an expiration date for the add-in. Do you know if there is an easy way to do these?
@KirkKuykendall1 I think we use active directory and, this solution would be really nice. It has some advantages as well. However, I don't get along with IT guys. I will have less control, have to wait, get questioned etc.. so, I went by @GKmieliauskas solution. I appreciate it anyway.
We use third party software key for generating id and checking for expiration date. Then we disable/enable extension on software key checking results.
@GKmieliauskas Do you mind sharing the software name and how it works? I was thinking of creating a list of alphanumeric strings and read/mark those from a live Google doc or something but your way is more robust, easier and less time consuming
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
