Open Forum

Expand all | Collapse all

Electronic invoicing and encryption management - Consequences?

  • 1.  Electronic invoicing and encryption management - Consequences?

    Posted 7 days ago
    We are setting up electronic invoicing, and when configuring the Document Exchange Service Setup, I get a message that NAV recommends that we enable Encryption Management.

    What would this actually do? I wouldn't mind using SSL to send electronic invoicing, but I'm concerned about the potential wider effects of this setting. For example, I wouldn't want to encrypt all the data in our database.

    I've done some googling, but I can't figure out what this setting actually does.

    Thanks.

    ------------------------------
    Dianne Butterworth
    Business System Manager
    The King's Fund
    London
    United Kingdom
    ------------------------------
    NAVUG Summit - Post


  • 2.  RE: Electronic invoicing and encryption management - Consequences?

    Posted 6 days ago
    Enable encryption is something that will encrypt information and will not allow unauthorised user to read Information.You can encrypt data on the NAV Server(Using the Data Encryption Management page) by generating new or importing existing encryption keys that you enable on the NAV Server instance that connects to the database.
    For Document Exchange Service Setup ,It is recommended to use encryption to protect the logon information like Consumer Key,Consumer Secret,Token,Token Secret.

    ------------------------------
    DEEPAK KUMAR
    BC/NAV Consultant
    AlleTechnologies Inc.
    ------------------------------

    NAVUG Summit - Post


  • 3.  RE: Electronic invoicing and encryption management - Consequences?

    Posted 6 days ago
    Thanks for the quick response, Deepak.

    While I do want to protect the logon information, I wanted to understand the wider consequences of enabling this setting.

    Does enabling this merely allow for the possibility of encrypting data, but I (or rather our Microsoft Partner) have to code the use of the encryption key on the necessary data? How would this work when sending information to a third party, such as our electronic invoicing portal? Would it transmit the encrypted or decrypted login information?

    Is there a way to send this information via SSL instead?

    Thanks.

    ------------------------------
    Dianne Butterworth
    Business System Manager
    The King's Fund
    London
    United Kingdom
    ------------------------------

    NAVUG Summit - Post


  • 4.  RE: Electronic invoicing and encryption management - Consequences?

    Posted 5 days ago
    Hi Dianne,

    Once you enable the encryption management in your NAV database it wouldn't encrypt all the data you need to do some code by using encryption management functionality available in the database. If you export NAV encrypted data for importing that on a new NAV instance, you've also to export the encryption key and import it on the other NAV instance (or you can't read that data).
    In case of sending information to a third party by using web services,it is advisable to use SSL.
    SSL is a web protocol that encrypts data that is transmitted over a network to make the data and the network more secure and reliable,You can enable SSL for web services (SOAP and OData)

    ------------------------------
    DEEPAK KUMAR
    BC/NAV Consultant
    AlleTechnologies Inc.
    ------------------------------

    NAVUG Summit - Post


  • 5.  RE: Electronic invoicing and encryption management - Consequences?

    Posted 4 days ago
    Thanks, Deepak. That's very helpful. It's clear now that I need to refer this to our MS partner!

    ------------------------------
    Dianne Butterworth
    Business System Manager
    The King's Fund
    London
    United Kingdom
    ------------------------------

    NAVUG Summit - Post


If you've found this thread useful, dive deeper into User Group community content by role