I have two same application published in IIS in under different web sites and ports:
http://myapp:82
http://myapp:83
I have the same membership connections strings in each application. When i get list of users from db I see users which created in another web site. As I know IIS automaticaly must categorize via ID membership information. But I haven't isolation between my apps.
I don't want to see membership data from another application.
I believe you can use the applicationName property when defining the membersip settings in web.config.
Here is the applicationName article on msdn
Related
Is there any possibility to configure IIS server to enforce Azure Active Directory authentication in hosted application? I don't want to apply any changes to app's code, it would be great to provide this authentication only on server level/layer (configuration IIS). Is this even possible?
EDIT
I have situation like this:
Have many applications from a customers. Have Azure AD and users added there. I need to provide Azure AD authentication to these applications. Moreover, i shouldn't do anything with code of these applications so i thought that i can try to enforce authentication not on application level but on server level. I've been searching informations about possibility of this method but can't find any (only application scenarios supported by Azure AD https://azure.microsoft.com/pl-pl/documentation/articles/active-directory-authentication-scenarios/ ). The only thing i have found is Azure Multi-Factor Authentication but i don't think it is helpful.
We tried to find it, and all that i have found that there is no possibility to enforce AAD authenticatoin on the IIS level and that it should be set up on the application layer which is actually the only one recommended and described process on the sites and in the AAD-related articles. I would say, that it can be even hard from a technological standpoint.
Reference 1
Reference 2
I have recently started working on Sharepoint 2010 and created a 3 tier test setup (server1- WFE and CA, server2- running all service applications, server3- Database server). I used powershell commands as listed in this blog to first create the admin and config databases. After that i used the Farm wizard to provision all the service applications.
After completion all the service app DB names have GUIDs. In IIS 7, all the application pools and the virtual directories under Sharepoint web services have GUIDs. Also all the service apps are running in the same user id (domain\spservice) and i am unable to change the id for some of the services.
I want to recreate my environment and not have any GUIDs, neither in the DB names nor in IIS. I have not been able to find any documentation on how to create all the service application DBs and IIS app pools without GUIDs. The one article i found mentions how to remove the GUIDs after installation. (I am left wondering if all production sharepoint 2010 farms out there really use GUIDs in DB names and in IIS (app pools, virtual directories)!?)
Can someone please direct me to an article that outlines steps to configure a complete sharepoint 2010 environment without GUIDs in DB and IIS?
When i started out on the initial test setup I used the Farm Configuration Wizard which creates almost all the databases with GUIDs and all those GUIDs can seem overwhelming for managing the environment, for documentation etc.
To answer my question in short- the sharepoint databases can be created without GUIDs (using powershell). However in IIS, the creation of application pools and virtual directories in IIS for the service applications will have to be with GUIDs. There is no alternative for that.
I followed the steps in the article here for initial install and then used the script to create service applications from this technet article making the necessary server and database name changes.
With most of my experience as a windows web farm administrator and managing uniform naming conventions the GUID names seemed annoying initially! But since there is very little to manage or troubleshoot from the IIS interface, we do not have to worry about app pool names and vdirs with GUIDs. It is all about ULS logs, event viewer and Central Administration site!
What would be the best way/ steps to create a SHAREPOINT 2007 SITE which any one can browse through in our situation?
We already have a web application in our production which is used as a authoring site and a extended application for that site collection, were the public can access it without authentication.
Can I create another SITE COLLECTION under the current web application and then create a required web page in it?
Thanks
Jag
You can create many site collections per web application. Just go to the Central Administration console and under Sharepoint Site Management, (Under Application Management), click Create site collection. You will then be asked to select the web application under which you want to create it.
Note too that the url will appear something like webappname/sites/sitecollection
hope this helps,
sivilian
Why do I need to create Multiple SSPs in MOSS?
My manager (sharepoint administrator) asked me to create another SSP which he wanted to use for TOP Management users. He didnt tell me what was the reason for it.
I was wondering what all scenarios we need to create Multiple SSPs. Any ideas?
Very vague question, please add more info!
And as a general answer, you don't need to, the concept is to share the services under the SSP between multiple web applications, what scenario do you have to need to create more than one?
Edit after question update:
An SSP host the services that will be used ( consumed ) by any associated Web applications. These services include :
Profiles
Audiences
Business Data Catalog Connections
Search and Indexing
Single Sign On
Excel Services
Usage Reporting
Source
So if your manager won't actually have something special on any of those services, I don't see a reason to do it. We had a customer once that needed the entire mysite and profiles customized, so we created a SSP just for that one web application.
We're trying to setup an internet facing WSS 3.0 site without Active Directory. We have a single WFE and a single SQL Server (2005). The WFE will be outside our DMZ.
We've successfully created the Central Admin site with a local admin account on the WFE and a separate account on the SQL server for the database, but we're stuck on setting up the WSS search capability.
I couldn't seem to get things to work when using Central Admin to start the WSS Search service. I'm thinking I'll need to use stsadm -spsearch to set up the WSS search manually, rather than using the menus in Central Admin.
Does anyone have any tips and/or resources they recommend?
You want to setup your WSS3 site using Forms Based AUthentication, with an ASP.Net SQL Membership Provider and backend database.
Microsoft have a very nice guide on MSDN.
I followed this guide when attempting something similar. This explains how to allow forms based and AD authentication on the same site but you could just follow the parts that explain how to setup forms based.
This also includes changing the web.config file for central administration so that it can access the SQL database used to store users for forms based authentication.
It is very easy to follow.
We're looking for the same... rather we have a separate AD for our DMZ, however, for the extranet, would like to use it without AD accounts. May I ask what you've come up with so far?
Have seen posts talking about local machine accounts, but we do have 2 app servers and realize the maintenance involved to keep them in sync if we use local machine acounts. Swore I saw a 3rd party tool that would allow user's to be added into their own db and managed through their web-part/portal but can't seem to find it now.