Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.7K 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
- 317 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.6K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
More Security Problems in Nav4 - roles not working(win auth)
sdcharle
Member Posts: 19
We are using Nav 4.0 (SQL Server), and our partner has recently started the process of setting up various roles for our users.
They have observed that the roles appear to work for users with database Authentication, however, for users with Windows Authentication, the roles don't seem to be working (the users are allowed to do things which should be forbidden).
Has anyone else experienced this? If so, how does one resolve it? We really do not want to have to use database authentication for our users, for a number of reasons.
Also, we have encountered the issue with having to do a (20+ minute) security synchronization in 4.0 everytime you change anything security related, but there still seems to be a problem.
Thanks,
Steve
They have observed that the roles appear to work for users with database Authentication, however, for users with Windows Authentication, the roles don't seem to be working (the users are allowed to do things which should be forbidden).
Has anyone else experienced this? If so, how does one resolve it? We really do not want to have to use database authentication for our users, for a number of reasons.
Also, we have encountered the issue with having to do a (20+ minute) security synchronization in 4.0 everytime you change anything security related, but there still seems to be a problem.
Thanks,
Steve
0