Thanks for your help,

Unfortunately, my _basicsecuritytest.cfm seems to be correct.  I guess MM
have added this to the 1.5.2 updater.  Which leaves me in the same
situation.  I'm actually very surprised that so few people have posted
install problems.  

My problem is in _securitytest.cfm line #39 where the installer creates a
new user, and attempts to authenticate him.  This fails.  I can't work out
why though.  I'll try and re-enter the passwords in the CFAdmin, but I guess
this may not be necessary, since 1.5.2 doesn't use siteminder any more.

Any more ideas, people?  Please?


Tony

-----Original Message-----
From: Kurt Mossman [mailto:[EMAIL PROTECTED] 
Sent: 27 October 2003 22:54
To: Spectra-Talk
Subject: RE: Spectra 1.5.2 Install Problems


Just a confirmation that Mark is correct... it was named
securitycontext="#scName#" and should be named name="#scName#". 
This was Macromedia bug 49942. 

-Kurt. 

-----Original Message-----
From: Marc Straka [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 27, 2003 5:32 PM
To: Spectra-Talk
Subject: Re: Spectra 1.5.2 Install Problems

We encountered this same problem. I was searching for documentation on this
problem, but can't find it. That being said, I believe this will fix the
step 5 error. Compare this code to what exists in
allaire/spectra/install/substeps/_basicsecuritytest.cfm. If I remember
correctly, the attribute called "name" is called something else in the
original file, but "name" is what actually needs to be used. This is from
line 71:

                        <cfa_NewInternalAdminSecurity 
                                action="addSecurityContext" 
                                name="#scName#" 
                                description="#scDesc#" 
                                Update="no">

So if #scName# is being passed with an attribute that is called something
else, try renaming the attribute to "name" as above and see if that fixes
it.

We also had problems with the login after the upgrade. One thing to try is
to re-enter the username and password information on your User Directory
datasource in the CF Admin. 

Good luck!

-Marc

[EMAIL PROTECTED] writes:
>I am attempting to migrate my Spectra 1.5.1 applciation to 1.5.2, 
>however cannot get the initial Spectra install
>(localhost/allaire/spectra/install/) to complete.
>
>I am having particular problems with authentication, and getting the 
>installation to complete.  The installer aborts at step 5 
>(_securitytest.cfm), then reports that it is unable to create and then
>authenticate a user.   Cfa_authenticate seems to not be working correctly.
>
>I cannot see any obvious answers to this, I've provided the correct 
>passwords to the user directories in the installer, but they seem to be 
>wrong when performing the authentication.  Having dug deeper, the 
>details appear to be held in Server scope variables, but are encrypted. 
>If I hard-code the password, this seems to work successfully.  I cannot 
>get the installer to authenticate against my UserDirectories.  Are 
>these variables held in the database anywhere?  Can I flush the Server 
>Variables by any means?
>
>I'm somewhat stuck, and any assistance would be hugely appreciated.
>
>Many Thanks
>Tony Pimm


=====================
Marc Straka
Web Applications Engineer
Nolo




~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
This list and all House of Fusion resources hosted by CFHosting.com. The place for 
dependable ColdFusion Hosting.
http://www.cfhosting.com

Message: http://www.houseoffusion.com/lists.cfm?link=i:17:5502
Archives: http://www.houseoffusion.com/lists.cfm?link=t:17
Subscription: http://www.houseoffusion.com/lists.cfm?link=s:17
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=<:emailid:>.<:userid:>.<:listid:>

                        
------------------------------------------------------------------------------
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.

Reply via email to