We are developing multilingual site using SharePoint 2007. Now the requirement from client is whenerevr user access the site, the Site should be open in his browser using users browser Language Preference. Our current site is in English and Spanish. If users language preference is Spanish then Spanish site should be display to the user.
Thanks in Advance
You need to develop a redirector module which will read the browser settings on the redirect.aspx page (Example) and then redirect to the appropriate language site based on thei site.
See here for the example:
http://panvega.wordpress.com/2008/05/15/variationrootlandig-redirect-to-another-variation-site/
Related
We are willing to implement a web application with edit functionalities of WORD documents using WebDav.
We are starting to have a better picture of the implementation required however, we have read on your site (http://www.webdavsystem.com/server/documentation/ms_office_read_only) that it is possible to avoid MS office Word login dialog to open when URL-authentication is implemented.
We can hardly find solutions on how to achieve this or on how to use URL-authentication with MS Office.
Would you be able to point us in the right direction with this process or even let us know how to get some examples on that?
Here are some options to avoid login dialog:
Implement URL authentication. You will need to include some session
ID in the URL. Note that you will need to include it in path. For
example:
https://server/[SessionID1234567890]/path/file.docx
Do not include your session ID in the query string, as MS Office will
truncate it when saving a document.
Implement cookies/Forms authentication. In this case you will need the IT Hit
WebDAV Ajax Library to open documents for editing. You will also need to install the protocol application (Edit Document Opener, supplied with the WebDAV Ajax Library) on a client machine.
Implement MS-OFBA authentication. You can generate sample MS-OFBA
code using 'Add WebDAV Server Implementation' wizard for Visual
Studio supplied with IT Hit WebDAV Server for .NET SDK.
Note that MS-OFBA will display an HTML login dialog inside MS Office UI, which is rendered by Internet Explorer. If you open a document from any other web browser the login dialog will be always displayed during first open.
To avoid login dialog during subsequent access you will need to set permanent
authentication cookie (check the 'Keep me logged-in' checkbox).
Use Kerberos authentication. By default Kerberos authentication will display login dialog during first document access only. This option can be configured in Active Directory policies.
I have the following architecture:-
Active directory server
IIS which will host asp.net MVC
Both the Active directory and the MVC web application are inside our company intranet.
I set the Asp.net MVC authentication type to be windows based.
But I have these questions:-
If our company employees tries to access the asp.net MVC web application from their home using their personal PC; will windows authentication work?
If the above answer is Yes; then how they will be typing their usernames, Something similar to username# domain.com ?
According to my above requirements, should I consider having form based authentication that is connected to AD? Instead of using windows based authentication?
Thanks for any help and advice
Best Regards
Assuming your website in IIS is visible to the outside through the firewall, then yes it will be accessible from home
depending on the browser, you should get a pop up asking for username and password, and the username should be typed
MYDOMAIN\JOEBLOGGS
This setup may well work fine but it depends on your needs - is your network admin happy to open this server up to the outside world
There can be a quirk if using Internet explorer externally, where IE does not display a pop up box, and instead tries to authenticate with the local windows username, which may not match AD username if it is a personal PC (to get around this on the client, go to Internet Options > Security > Custom Level then scroll down to User Authentication and select 'Prompt for username and password'
We have a ASP.NET MVC3-Application which includes a lot of links to Documents in SharePoint 2010 - Libraries. If the User clicks on one of these links, he'll be invited to choose between ReadOnly-Mode or Edit-Mode of the Office-Document. If he chooses "Edit-Mode", he will have to enter the credentials for SharePoint.
Is it possible to do some kind of SingleSignOn out of the MVC-Application, using the Users MVC-App-Creentials to log into SharePoint2010? We'd like to have the user clicked on the link and to be able to edit the document and click save (saving back to SharePoint) without entering his credentials once again. Are there any experiences?
//edit: the MVC-Application & SharePoint are both in a different Active Directory than the User, so this problem is not solvable by implementing a User > SharePoint SSO. Further it is not possible to access SharePoint through the SharePoint Server Object Model in the MVC3-Application: SharePoint uses .NET 3.5 and MVC3 requires .NET 4.0
You can achieve what you are trying to do, however, you would need to enable claims based suthentication on SharePoint and write a custom provider.
One of the possible solutions in your case is Active Directory Federation Services.
http://blogs.technet.com/b/andrew/archive/2010/06/09/what-is-adfs-and-why-you-should-care.aspx
I am just getting into Sharepoint, and I have a question about having a Sharepoint internet site, and a Sharepoint intranet site.
Is it possible to have an internet site, and have a login type function, that when the user logs in, they are taken to a site like the Team Site? I think I'm trying to integrate an internet/public site with the Sharepoint functions that users are familiar with in an intranet site.
My goal is to have non-private info on the internet, but once authenticated, the user would be able to upload docs, search docs, see a calendar, that sort of stuff.
Maybe I am not totally clear due to my lack of understanding thus far of Sharepoint?
The google keyword here is Forms based authentication.
Here is a good post to start you off and a second including Mysite setup
I'm learning the difference between these to concepts.
I want to build a public Sharepoint site, and is one better than the other for this use, or is it too general of a question?
At a very general level; application pages are stored on the web server's file system (also known as the "12 hive") and run in a more priviledged security context. You tend to use these to create administrative interfaces.
Site pages (such as default.aspx) are user-targeted, and available for customization via SharePoint designer.
Site Pages can contain one or more webpart zones each zone may contain one or more webpart zones.
Site pages can customized
Site Pages not supprot code behind file.
Application pages such as Create.aspx,Themeweb.aspx.
Application pages Can't customized
Application pages support code behind file.
Site Pages:-
Site Pages are Site or Web Scoped,
User can customize Site Pages,
Site Pages are stored in Content Database,
You cannot have custom code in Site Pages,
Site Pages are Un-ghosted Pages.
Application Page:-
Application Pages are farm scoped,
No customization can be done by the user,
Application Pages are stored in WFE(Web Front End) in _layouts folder,
You can have custom code in your Application Pages,
Application Pages are Ghosted Pages.