NAV 2015/2016 Encryption
rsaritzky
Member Posts: 469
Hi all,
We're upgrading from NAV2015 to NAV2016. Currently we have a custom "Private Info" record that encrypts some name and address information. We currently use a third-party addon's encryption routine. The third party has changed their encryption routine in 2016, so we have to re-encrypt this data.
So this looks like a potential opportunity to change our custom table to use NAV's standard encryption routines.
Here's my question - I've read about NAV encryption and watched some instructional videos. The examples say to use BLOB fields to store the encrypted data - I understand that. However, our current custom table just has some long-ish text fields to store the encrypted data - 75 characters for a 30-character text field and 250 characters to encrypt an 80-character text field.
I would prefer to keep the same table structure rather than change all the encrypted fields to BLOB. However, I'm concerned that 75 characters might not be sufficient length to store a 30 character field using NAV's standard encryption.
Does anyone have experience to know the length of NAV's encrypted values? I certainly can test it, but just asking if anyone knows.
Thanks
Ron
We're upgrading from NAV2015 to NAV2016. Currently we have a custom "Private Info" record that encrypts some name and address information. We currently use a third-party addon's encryption routine. The third party has changed their encryption routine in 2016, so we have to re-encrypt this data.
So this looks like a potential opportunity to change our custom table to use NAV's standard encryption routines.
Here's my question - I've read about NAV encryption and watched some instructional videos. The examples say to use BLOB fields to store the encrypted data - I understand that. However, our current custom table just has some long-ish text fields to store the encrypted data - 75 characters for a 30-character text field and 250 characters to encrypt an 80-character text field.
I would prefer to keep the same table structure rather than change all the encrypted fields to BLOB. However, I'm concerned that 75 characters might not be sufficient length to store a 30 character field using NAV's standard encryption.
Does anyone have experience to know the length of NAV's encrypted values? I certainly can test it, but just asking if anyone knows.
Thanks
Ron
Ron
0
Best Answer
-
NAV max text length is 250. So you would need two fields to store the data.5
Answers
-
The NAV Encrypt encrypts the data no longer than 215 of length and resulting string is always based on my experience 345 characters0
-
NAV max text length is 250. So you would need two fields to store the data.5
-
Rashed,
ThanksRon0
Categories
- All Categories
- 75 General
- 75 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 610 NAV Courses, Exams & Certification
- 1.9K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 251 Dynamics CRM
- 103 Dynamics GP
- 6 Dynamics SL
- 1.5K Other
- 991 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 28 Design Patterns (General & Best Practices)
- Architectural Patterns
- 9 Design Patterns
- 4 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1K General Chat
- 1.6K Website
- 77 Testing
- 1.2K Download section
- 23 How Tos section
- 249 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
