Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Encrypt Web.config.Encrypt Web.config.
Previous
 
Next
New Post
8/6/2009 4:50 AM
 

Hi,

I want to encrypt my web.config of my dnn website. Especially the server connection string and other customer parameters. How can do it in Dotnetnuke architecture?

thanks

 
New Post
8/7/2009 2:37 AM
 

You would do this just like you would any other .Net projects web.config.  See the following post by Scott Gutherie about this very issue.

Encrypting Web.Config Values in ASP.NET 2.0

Of course, before you do anything like this you want to make a backup of any files that you update.  Otherwise, you might really mess things up and take the whole site down.  Even on a dev box I'd recommend making a backup, becuase who want to have to rebuild a site when it could have been avoided.

 
New Post
8/7/2009 11:25 AM
 

actually you can't just do it as standard asp.net 2.0, as our providers extract aspects of the connection string. You would need to make an alternative version of the dataprovider that was aware of the encryption to ensure it could read and decrypt. Alternatively there are a few commercial modules that do this, I have not had an opportunity to evaluate any of them though.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
8/7/2009 11:42 AM
 

I have successfully encrypted the main database access in a DNN web.config as high as 4.9.4 using the command line details outlined in this article
http://aspnet.4guysfromrolla.com/demos/printPage.aspx?path=/articles/021506-1.aspx 

Here are my two working command lines (note that I added the location of aspnet_regiis.exe to my path).  Note that you must do both connectionStrings and appSettings (if still used).  Please do read the linked article thoroughly, it is very well written and explains everything really well.

C:\>aspnet_regiis.exe -pef "connectionStrings" "D:\Webspace\domainname.com\web" -prov "DataProtectionConfigurationProvider"
Encrypting configuration section...
Succeeded!

C:\>aspnet_regiis.exe -pef "appSettings" "D:\Webspace\domainname.com\web" -prov "DataProtectionConfigurationProvider"
Encrypting configuration section...
Succeeded!


- Accuraty / Jeremy
 
New Post
8/9/2009 11:49 PM
 

cathal connolly wrote

actually you can't just do it as standard asp.net 2.0, as our providers extract aspects of the connection string. You would need to make an alternative version of the dataprovider that was aware of the encryption to ensure it could read and decrypt. Alternatively there are a few commercial modules that do this, I have not had an opportunity to evaluate any of them though.

Cathal

So what about how we are extracting the information in our data provider makes it so it does not work with how you would do this with a standard asp.net 2.0 appliction?  I was alwasy under the impression that as long as you used the build in fucntions to read the data from the web.config that it would read/decrpty the data correctly.  I can honestly say that I have not tried it, so now my interested is peaked and I might have to play with this feature some.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Encrypt Web.config.Encrypt Web.config.


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out