FlexWiki is simply using the standard ASP.NET 2.0 Authentication
mechanism - I would suggest that the hosting orgs are being overly
restrictive in not providing the means to use SQL Express, etc., but
that't their perogative and it doesn't help your circumstance. As to why
does FlexWiki not provide an alternative mechanism - simply put, because
it hasn't been a priority that has been raised by the user community,
decided upon by the community or contributed by the community (at least
not any postings I have seen). Craig Andera has been labouring away at
shipping a .NET 2.0 version with very little assistance and although
there has been periodic contributions from others, in recent times he
has been doing the lion's share of work. As such, it has taken him
nearly 2 years to complete the effort (apparently he has other things to
do than just code FlexWiki :) I don't think anyway can critisize his
contributions, nor what he chooses to work on.
The good news is that ASP.NET 2.0 utilizes a provider model to abstract
a number of services that include the membership and roles capability
that means an alternate solution may be coded and added. If this is one
of the major areas that impacts your ability to use FlexWiki, then
perhaps this is one of the places where you and your company can
contribute. There are many tutorials, etc. on the web that describe in
detail how to create custom implementations of the membership and role
providers [1]
[1] http://www.devx.com/asp/Article/29256
<http://www.devx.com/asp/Article/29256>
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Qasper Tech Support
Sent: Thursday, August 16, 2007 10:13 AM
To: 'FlexWiki Users Mailing List'
Subject: Re: [Flexwiki-users] How to setup Flexwiki for external Sql
Server
HI,
WebHost4Life, Verio, GoDaddy and other public sites we use do NOT allow
the execution of standalone executables (aspnet_regsql.exe) nor do they
allow or provide access to the Framework version folders. Also, they
won't run it even if requested since it apparently affects all users
using the framework.
Why is FlexWiki using this method and not providing an alternative? This
is really restrictive and simply makes it impossible to use the desired
functionality of FlexWiki. Isn't there some other way that FlexWiki can
be coded so that, if there's a connection string in the web.config, it
will use that instead of creating one on-the-fly?
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Jeffery Seiffert
Sent: Thursday, August 16, 2007 8:55 AM
To: FlexWiki Users Mailing List
Subject: Re: [Flexwiki-users] How to setup Flexwiki for external Sql
Server
Hi, what is happening is that the database that comes with Flexwiki is
used for SQLExpress. SQLExpress will auto-attach the database to its
self to the SQL Service that is running. The full version of SQL Server
does not auto-attach databases.
I have this same problem on my local computer because I don't have
SQLExpress but the Full SQL Server version.
So what you have to do is basically this:
1. Have WebHost4Life setup a database for you.
2. Once the database is setup you need to run the aspnet_regsql.exe to
setup all the membership stuff. It's in the
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ folder.
It does have a gui interface but you will have to do this from the
command line because your going to an external SQL Server. You will
need to tell it the address of the server the database name and the
login information.
I think running aspnet_regsql.exe -h will give you the help
information.
3. Now you will need to modify the Web.config file.
Create a ConnectionStrings Section for the Database Connection:
<connectionStrings>
<add name="SqlConnection" connectionString="Data
Source=myserveraddress;Initial Catalog=MyDatabase;Persist Security
Info=True;User ID=myuserid;Password=mypassword"
providerName="System.Data.SqlClient"/>
</connectionStrings>
You will need to enter your Data Source, Initial Catalog, User ID, and
Password for your system.
You will then need to change the connectionStringName to "SqlConnection"
in the Membership providers section of the Web.config if you used the
configuration above.
Next you will need to change authentication mode to Forms.
4. With this done and if all the settings are correct, you should be
able to run Flexwiki without errors.
5. The only hard part left is to add users to the membership database.
I say hard because I don't believe that Flexwiki has an user management
system in place yet.
So there are a couple options. (I'm not sure all of them will work
though.)
A. You could get the Flexwiki source and pull it in to Visual Studio
2005 and use the ASP.NET Configuration to create users. Make sure to
copy the updated web.config to that code other wise it won't be able to
find the SQL server to manage.
B. Create a new web project in VS 2005 and add the Flexwiki web config
to it and use the ASP.NET Configuration interface.
C. You could use something that will run stored procedures on the server
and find an run the Add user stored procedure.
6. As far as Flexwiki security goes, I haven't played with it so I can't
help you on that, but hopefully you will be able to run Flexwiki and
check it out.
I hope this helps and if anyone sees that I missed anything or said
anything incorrectly please let everyone know.
Thanks,
JefferyS
Qasper Tech Support wrote:
Has anyone successfully deployed FlexWiki to a public host and has used
the user registration feature? Even though App_Data is RWXD,
WebHost4Life tech support claims that creating a database on-the-fly and
writing to it like App_Data (ASPNETDB.MDF) in FlexWiki does is not
secure and they can't support it (I can sort of understand that. They
run all databases on separate, secure servers).
We have to open a proper database on their separate servers (which is no
particular problem for us).
What is the alternative in FlexWiki to creating and writing to the
on-the-fly database? Is there a connection string somewhere we can tap
into and direct all db action to another database?
________________________________
------------------------------------------------------------------------
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
________________________________
_______________________________________________
Flexwiki-users mailing list
Flexwiki-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flexwiki-users
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Flexwiki-users mailing list
Flexwiki-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flexwiki-users
