Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 304 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Homemade registration tool for parts of NAV2013
Jocafe
Member Posts: 10
Hello folks,
I need some advise regarding some "home made" registration tools for NAV2013.
Scenario:
We are developing an add-on for NAV2013 (having done the whole process Microsoft requires). This solution we are creating is basically a group of smaller ones. Some of them bigger (as in they are more complex, do more tasks and have a "name" by themselves) and some of them smaller (as in they are modifications/improvements on the standard NAV instead of additions).
So far so good!
We find now that we would like some of those smaller solutions that are a part of the bigger one (to be precise the solutions that have a "name") to be available or not depending on the client and the contract between us. Now, the first thing that came to mind is creating another add-on but we'd rather not have to do the whole process again for each smaller solution. Plus, it's not the cheapest thing to do either.
Now I find myself trying to figure out a way to "register" parts of NAV "at will". What I thought of at first was some sort of client/server authentication. Meaning the client connects to us during the installation process and we provide a valid key. We don't really like that idea due to the uncertainty that that key won't be used again on a different client (not likely, I know, but still doesn't feel "fullproof"). And with that the options related to putting that info into the SQL server were discarded.
The tools I have on the table are:
- NAV itself (2013) with the possibility of adding new objects
- DLL development (I thought of maybe doing something with SQL assemblies)
- The possibility of creating maybe a small program to do that, but I can't think of a way to store that "everything is ok and valid" info in a secure and cannot be duplicated and sent to someone else to install (for it won't work).
- Probably something else I'm forgetting.
Ideally we'd like the simplest way that would require the process to be performed just once on the server and not every workstation and would allow us to generate keys without having to change a thing.
I hope I was clear enough. Thank you!
I need some advise regarding some "home made" registration tools for NAV2013.
Scenario:
We are developing an add-on for NAV2013 (having done the whole process Microsoft requires). This solution we are creating is basically a group of smaller ones. Some of them bigger (as in they are more complex, do more tasks and have a "name" by themselves) and some of them smaller (as in they are modifications/improvements on the standard NAV instead of additions).
So far so good!
We find now that we would like some of those smaller solutions that are a part of the bigger one (to be precise the solutions that have a "name") to be available or not depending on the client and the contract between us. Now, the first thing that came to mind is creating another add-on but we'd rather not have to do the whole process again for each smaller solution. Plus, it's not the cheapest thing to do either.
Now I find myself trying to figure out a way to "register" parts of NAV "at will". What I thought of at first was some sort of client/server authentication. Meaning the client connects to us during the installation process and we provide a valid key. We don't really like that idea due to the uncertainty that that key won't be used again on a different client (not likely, I know, but still doesn't feel "fullproof"). And with that the options related to putting that info into the SQL server were discarded.
The tools I have on the table are:
- NAV itself (2013) with the possibility of adding new objects
- DLL development (I thought of maybe doing something with SQL assemblies)
- The possibility of creating maybe a small program to do that, but I can't think of a way to store that "everything is ok and valid" info in a secure and cannot be duplicated and sent to someone else to install (for it won't work).
- Probably something else I'm forgetting.
Ideally we'd like the simplest way that would require the process to be performed just once on the server and not every workstation and would allow us to generate keys without having to change a thing.
I hope I was clear enough. Thank you!
0
Comments
And I think we are going the same route.
Or parhaps let the customer request a key online (from inside nav of course)?
Validated against License No. or License customer name.
Johannes Sebastian
MB7-840,MB7-841
But how can I get that info from within NAV (the license key or the customer name set on the license)? Would I have to use a third-party DLL to accomplish that?
I know I can check on a virtual table the objects and the permissions of each one but I do not know a way of getting that info from within NAV.
And before I forget, thank you for your answer and idea!
Thanks!