As far as I know both FireFox and Safari can not work with Kerberos in a SharePoint context for the time being, but why is that, and should we expect that both FireFox and Safari will play ball in the SharePoint 2010 timeframe?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
As far as I know both FireFox and Safari can not work with Kerberos in a SharePoint context for the time being, but why is that, and should we expect that both FireFox and Safari will play ball in the SharePoint 2010 timeframe?
All information on SharePoint 2010 is currently under NDA until late October (except what you can see on the sneak peek) so no-one will be able to officially answer your question at this time.
However there is very unlikely to be any difference for the 2010 version from SharePoint 2007. Kerberos is supported by the product but its actual behaviour within a Windows network is determined by the current implementation used in Windows Server today. This is not related to SharePoint but the use of Kerberos within IIS ASP.NET applications. So don’t expect anything to change here on the server side.
For the client side, that’s entirely dependent on the development priorities in the Firefox and Safari teams. For Firefox, search for and vote on the bugs with Kerberos you’d like fixed. You may be able to contribute and assist with the fixes as well.