I came to an interesting way to solve the following problem and I should know if I have a The better way is the objective.
Actually, I'm making a basic CMS system that users can register for their microsite and create their own users. I'm using the asp.net subscription API.
I want one way to isolate the users of different microsites from each other so that a user can be certified with www.mysite.com/johns-site www.mysite.com/pauls-site . Can be certified with.
I also wanted a way to associate a user name with a microsite, so that a user has been registered as Bob on a site, this is not being shut down to another user. A separate microsite is registered as Bob.
To achieve this, I saw that the user in ASP membership tables comes under an application. Every time I receive a request, I have a method that switches to applicationName in web.config based on url.
It caters my objectives in an easy way, but seems a little hesitant. Is there an alternative way to switch applications to the membership provider?
It is possible to set up / set property property name on runtime However, according to the MSDN post below Not recommended because the property is not secure i.e. if multiple users are creating accounts for different applications at the same time, then they can not properly assign per user name.
Syntax:
Subscription. Application Name = "MyAppName" or
Subscription. Application name = "MyAppName";
Note:
You update the contents of the web.config file What are the application code? If this is the case then it is definitely "hacked" as well as editing any web.config, any active session will be skipped (if your app uses the session's status).
Comments
Post a Comment