Re: Testing SourceID.NEt v0.3 in windows 2003
David Waite <[email protected]> Thu, 07 Aug 2003 16:21:47 -0600
| Newsgroups | gmane.comp.sourceid.sso.devel |
|---|---|
| Message-ID | <[email protected]> |
I think you have just made a good argument for a developer README file in the next release :-) I currently follow a sightly different path: 1. Download SourceID to wherever is appropriate (I personally put it under c:\src; I'll use that below ) 2. Optionally, switch to a different X509 certificate pair. 3. Create "providers.xml" either by editing "providers.xml.dist", or by retrieving a copy from the PingID FederationManager. For development I usually set the names to "localhost", for interoperability testing I set them to an externally visible name. If you changed the certificate(s), the public key(s) needs to be listed within the providers.xml file. 4. Create the sp and idp "web.config" files by editing the web.config.dist files. 5. Verify that machine.config is updated. 6. Run sn.exe -Vr *,8c869275329aeb85 To have everything signed with the public key included be considered validly signed (not secure, but fine within a development environment) After this point, everything is tool-chain specific. For VS.NET 2003 I 7. Use iismgr.exe to make virtual directories for 'sp' and 'idp', mapping to c:\src\SourceID.NET\sp and ...\idp 8. remove and re-add the sp and idp samples, then I am good-to-go. If I'm using another tool-chain, I 7. Build the distribution with NAnt. 8. Use iismgr.exe to make virtual directories for 'sp' and 'idp', mapping to the NAnt-created c:\src\SourceID.NET\build\<version>\sp and ...\idp directories. I think I will just include portions of NUnit v2.0 in the next release to simplify things (so that the user doesn't have to download it separately). -David Waite [email protected] wrote: >I have just successfully installed the samples on .Net Server 2003. The steps - albiet informal for just now - are outlined below. >I think and iisreset is needed to allow the HTTP handlers to register - don't know if that *definitely* is the case, but certainly fixed it in my install. > >- Copied the idp and sp directories to the wwwroot folder. Rename them to idp-sample and sp-sample. > >- Use Frontpage Admin to create fp webs. > >- Copy providers.xml to both application directories. > >- Load .sln file and remove references to web projects and add my own references to sp adn idp i created. >Recompile and new assemblies are put into bin folders. > >- IISRESET in at command line. > >- Rename Web.config.dist to Web.config in both apps. > >- Change SourceID.Test Assembly Nunit 2.0 reference to nunit.framework.dll in prog files. > >- Changed all references to > >Microsoft.Web.Services.Security.XmlDsigExcC14NTransform > >... to > >Microsoft.Web.Services.Security.Xml.XmlDsigExcC14NTransform > >... as i am working with WSE2. > >- update machine.config using utility > >- sn.exe -Vr *,8c869275329aeb85 > >- copied key.pfx to each app > >- Changed reference to C:\... in web.config as i am on d drive. > >- Run and works. > >Regards, >Steven. >_______________________________________________ >sso-dev mailing list >[email protected] >http://mail.sourceid.org/mailman/listinfo/sso-dev > >