 | | | RE: Anyone working with DotNetNuke? | RE: Anyone working with DotNetNuke? 2004-09-30 - By Tom Ward
Nate,
I placed your second solution on our production server and it did not
cure what ales me. Still get following message as soon as I try to
login to the second application after linking to it from the first
System.Security.Cryptography.CryptographicException
Anything you can think of that I might be missing would be great.
These are the steps that I have taken so far:
1) Placed both applications in their own application pool in IIS.
2) Changed the security cookie in web.config of both applications.
3) Changed the Machine.config on the server as you suggested.
The application runs but crashes whey you submit from the login control.
I think there is something in the global.asax that is causing problem.
Still looking for the answer.
Thanks
Tom
-----Original Message-----
From: Nate Pink [mailto:nate.pink@(protected)]
Sent: Wednesday, September 29, 2004 3:25 PM
To: aspnet-admin@(protected)
Subject: [aspnet-admin] RE: Anyone working with DotNetNuke?
Tom and all,
The problem you are running in to is that the portals by default use the
same form cookie name. The web apps try to reuse it and finds they
can't decrypt it. There are two fixes for this that I know of.
One is to change the name of the form security cookie name in the
web.configs of the apps, but you will loose cross portal authentication
(which only really works if you make a custom authentication assembly
that pulls a user id from a common source).
The second is to set you web server machine to not encrypt form
authentication tokens per web application and instead do it for the
whole machine. This was a change from dotnet 1.0 and could be a problem
in a hosted environment if changed. To change this, you will need to
modify the machine.config: (this is from memory, but should get you
started)
<machineKey validationKey="AutoGenerate,IsolateApps"
decryptionKey="AutoGenerate,IsolateApps" validation="SHA1"/>
To
<machineKey validationKey="AutoGenerate" decryptionKey="AutoGenerate "
validation="SHA1"/>
My old job switched to a policy of "Everything fits in to a IBuySpy
Portal". I think it's great for some things, but tired of it quickly
and left the job when they wouldn't listen to reason. To do much of
anything useful you need to modify fundamental parts to it, which makes
upgrading to a new version all but impossible. I haven't used DNN in
production, but thought it was much cleaner than the original IBS
reference. It has some great code samples in it for sure. My new job
used it for what it was intended, a reference, and build a nice light
way template app from it.
Nate
-----Original Message-----
From: Tom Ward [mailto:TWARD@(protected)]
Sent: Wednesday, September 29, 2004 11:50 AM
To: aspnet-admin@(protected)
Subject: [aspnet-admin] RE: Anyone working with DotNetNuke?
Another Issue that I have yet to resolve which is a thorn in my side is
running multiple DNN applications on the same server. I have DNN
implemented multiple times on the same server and I can not link from
one DNN To the other. In fact if I run one application and close it
then run the other application it will fail with a "System Cryptography
error". I have to clear my cookies and files before it will run. I
must fix this problem but so far nothing I have tried has worked. I
will post the fix when I find it.
Tom
Need SQL Advice? http://sqladvice.com
Need RegEx Advice? http://regexadvice.com
Need XML Advice? http://xmladvice.com
Need SQL Advice? http://sqladvice.com
Need RegEx Advice? http://regexadvice.com
Need XML Advice? http://xmladvice.com
Need SQL Advice? http://sqladvice.com
Need RegEx Advice? http://regexadvice.com
Need XML Advice? http://xmladvice.com
|
|
|
