Tag Info

Hot answers tagged

4

You need to implement single sign on (SSO). Robert Bogue has a good step by step. http://www.thorprojects.com/blog/archive/2008/08/02/moss-single-sign-on-setup-step-by-step.aspx


3

All of that information could be gathered with Marc Anderson's SPServices library and jQuery, if you're running MOSS. Specifically you'd want to look at the SPGetCurrentUser information. With that, you'd be able to wire up the query string parameters and pass it along to the vendor.


3

There are two possible options If you don't have enabled IFD (and therefore claims based authentication), the simplest solution would be to configure IE, to pass the credentials of the current windows user to the site. Therefore you have to adjust the security configuration of the zone assigned to the SharePoint URL, to send the credentials of the current ...


2

Configure your ASP.NET web application to use Windows Integrated authentication, just like SharePoint. Furthermore, configure group policies so that the URL where your ASP.NET application is hosted is considered part of the Local Intranet. This will make IE pass the user's credentials to IIS by using Kerberos. Alternatively, you can configure the ASP.NET ...


2

You can do it by sharing a machine key: http://msdn.microsoft.com/en-us/library/eb0zx8fc.aspx Try to setup SharePoint for Forms Authetication. Follow steps from http://msdn.microsoft.com/en-us/library/bb975136.aspx Share same machine key between SharePoint application and ASP.NET application Make sure you have same Authetication cookie path. (You can ...


2

You could use an STS: Windows > ADFS Forms > custom one (eg http://identityserver.codeplex.com/ or create one) All SharePoint sites that make use of the same STS will effectively have SSO. A drawback to STS/Trusted Identity Providers is the bad People Picker experience; no resolving of partial entries, every mapped claim can be selected, ... Not a good ...


2

If you are just using the default Windows authentication this should not be a problem at all - even with claims based authentication. Make sure the SharePoint URLs are in the "Intranet Zone" of the browser and your users should be logged on automatically - even without Kerberos. For this basic scenario you don't need ADFS or any other identity provider.


2

OR...you could NOT use PORT numbers for your MySite web application and either create a unique URL like http://mysite or http://my (or whatever works for your organization and culture). Then set trusted sites. OR, If the users are non-domain users (the new domain will trip an auth prompt when you switch hosts) you could create the MySite host under a ...


1

Single-Sign-On (SSO) process authenticates recognized users and opens access to multiple applications, to which they have been granted rights. Logging in the first time authorizes the users to access all applications and enables them to switch between them as needed. The users then don’t need to enter their password each time. This lasts until the Users log ...


1

Unfortunately due to the 'home-realm discovery' set of challenges, there's no way Office 365 can know where your users come from in order to be able to transparently redirect them to your ADFS server for their logon token. This is because they cannot guarantee that the intention is to specifically logon with only the organisational account bound to the ...


1

SharePoint 2010 is weird with it's cookie issuing when you are using Claims - it's SharePoint's built-in STS that issues cookies, not the web application, therefore some settings you issue via the <forms /> tag don't have any effect. I had a similar problem but wanted SSO between many SharePoint web apps, what I did was I ended up creating a custom ...


1

You need to configure ADFS with SharePoint. Essentially its a type of Claims Authentication with a conceptual walkthrough mentioned here This is an excerpt from MSDN that explicitly mentions the flow of a single user from one web app to another in SharePoint Visiting Two SharePoint Web Applications In this walkthrough, John visits the a-Portal ...


1

You have to go to your Firefox address bar and type about:config. This will bring up the internal config editor, which allows you to set all kinds of properties that influence Firefoxs behavior. Look for the key called "network.automatic-ntlm-auth.trusted-uris". Set that keys value to a comma separated list of servers you want NTLM auth for. So if your ...


1

You will need to override the OnPreRender method to escape the single quotes: protected override void OnPreRender(EventArgs e) { if (!string.IsNullOrEmpty(_gridDS.FilterExpression)) { _gridDS.FilterExpression = string.Format( _grid.FilteredDataSourcePropertyFormat, _grid.FilterFieldValue.Replace("'", "''"), ...


1

I would rely on the same authentication mechanism (eg : ntlm if you're on an intranet) and work with subdomain - as suggested above by Eric - while targeting the cookie to the top level domain name. Alternatively, you can delegate this requirement to an external tool / system like Microsoft ISA / UAG, SiteMinder, F5 APM, EmpowerID, Oracle Identity ...


1

trick way use FQDN to access sp and .net site. e.g. sp.domain.com, web.domain.com write code run in sharepoint to write FBA cookie for current user, domain: domain.com or you can config asp.net app to use NTLM or config sharepoint to use CBA, and asp.net app use CBA, they use the same STS.


1

For SharePoint Server web applications running on Windows Authentication there is only one (very not recommended way) ... use basic authentication for the specific zone. The client will send username and password in cleartext (yes through a secure channel as it is HTTPS, but it is cleartext at the server side). Using sharepoint code running on the server ...


1

You could use SharePoint's SecureStore to map credentials and pass them to the .NET site. Another approach is configuring CLAIMs for both SharePoint and your .NET site and relay on the same IdentityProvider (such as ADFS in a Windows environment)


1

to be honest I've discovered this is out of the realm of SharePoint, we just needed something generating SAML tokens with 2 attributes in the assertions, it was easier to code something up using this componentspace.com/Products/SAMLv20.aspx. Thanks everyone for your help.


1

Thomas, you can use port 443 to this effect.


1

I believe your going to need to add ad fs to your plan. This should get you pointed in the right direction. http://technet.microsoft.com/en-us/library/dd857388.aspx



Only top voted, non community-wiki answers of a minimum length are eligible