So our issue is with the MOBILE login form in SharePoint 2010. We have FBA implemented and it works great for non-mobile users. It is a custom login that lets users switch between AD or FBA. But the issue arises with Mobiles (iPhone, Blackberry, Win Mobile, Android) when they hit the site.
How can I customize the mobile login screen for a sharepoint 2010 site? Has anyone done this?
Edit 1:
The default behavior of the mobile login screen is oddly only allowing the FBA users to login and not the A/D users.
Edit 2:
I know that my iPad works fine in Sharepoint 2010 using my A/D account on a custom login form. The problem arises when I go to the iPhone. So what you are saying is that the mobile login screen only supports FBA for a reason, A/D accounts won't work?
Edit 3:
We tested on windows phone 7 and it does support the standard login and does not automatically redirect to the mobile page. So Win Phone 7 is a non-issue. The main issue is iPhone and Android since they goes to the mobile login which is currently only supporting FBA users. Our custom non-mobile login form we created automatically handles A/D login based on custom code we wrote. Ideally we'd like to have mobile point to the custom login page we built. But we can't find how this is set.
For the benefits of others facing similar problem, here is our alternative.
In SharePoint 2013 Application Management, highlight your Web Application and select Authentication Providers. Select FBA and in the Custom Sign In Page and append "?mobile=0" to your FBA URL like this:
You don't have to create custom login screen.
Follow the steps below to open your web app. on Mobiles (iPhone, Blackberry, Win Mobile, Android)
Navigate to Inetpub (in default drive (generally c))
Navigate further to wwwroot\ws\virtualdirectories
Navigate to your application folder (port number specific)
Navigate to App_Browsers folder
Open compact.browser in notepad
Find "Iphone" or any other device for which you want your app. As result you will get to XML tag for iphone safari browser, see the sample below :
set the value false in following element :
likewise there is XML browser tag for each mobile device (android, BlackBerry, etc), just change the value of isMobileDevice to false
hope it helps
-- Sumit (courtesy Ishaan )
Related
We have a site used by Outlook addin hosted on sharepoint, when a user tried to access it they had a browser window open on the Sharepoint Online site, our front end is hosted there but it doesn't bring us to site location it just brings to Sharepoint home page.
We resolved this for a lot of users by adding runtimes in our manifest (this will force Outlook to use IE, whereas before browser is determined on a combination of 365 and windows versions). Still for some users it will bring us to a new browser, we have checked they are on the same Windows and Office 365 version as others who have the plugin working in Outlook task pane.
Also to note there is no issue with anyone using the plugin from OWA (web mail in a browser) and the redirect from desktop outlook looks like it for SSO then verifies user in browser and brings us to Sharepoint.
anyone have any idea what could be causing this?
The problem was caused by any sites or domains trying to be accessed by outlook addin need to be added to app domains in the manifest file. We ran a fiddler trace on the users machine and took a list of the domains that were being hit (for SSO) once we added them this issue was resolved.
We have created a customization to our site that needs approvals. When we go to the mobile application and the Approvals section, we see the item that needs approved but when we go to select the approval item, the following error pops up "Unsupported Protocol: The communication protocol used by the Acumatica ERP server to which you are trying to connect is not supported by the application. Make sure you use the latest version of Acumatica application." Our current site is running 17.206.0030. We can go to the approvals page thru the site and it works fine for the same custom approval. This error only occurs in the mobile application.
Mobile App Error Screen Shot
Last time I received the same error message in Acumatica mobile app, there was an issue with the changes, that I made in Mobile Site Map. Let me suggest to delete all Mobile Site Map customization files from the local website, restart the mobile app and try to open the Approvals screen on a mobile device.
If there will be no issues with the Approvals screen after you remove all Mobile Site Map customization files, you might consider applying different parts of your Mobile Site Map customization to determine what particular changes are causing this error. And in case of a Mobile Site Map customization built using MSDL, there is also a built-in option to enable MSDL interpreter logs, which are usually quite helpful to verify no errors have been produced by the MSDL interpreter.
Our environment is Sharepoint 2010, with a web application created (and site collection on top), using claims based authentication. The first site is using port 881. It is using integrated windows authentication. Another web application is created, extending the first application, using port 882. This site is using Forms Based Authentication, the membership provider is System.Web.Security.ActiveDirectoryMembershipProvider, named admembers. I have turned off Client Integration on both sites.
When I login to the 881 site, on my corporate network, logged into the machine with the same domain account that sharepoint uses, I can open an Office file saved in a document library, and it subsequently opens in the appropriate Office application, without asking me login again. But, If I login to Sharepoint from a computer that is not on our network, or login to the computer with an account that is not a domain account, I get prompted again to login when openning an Office document. If I choose the option to save, it does not prompt, but if I choose open in the dialog window, I am forced to enter my domain credentials again.
When I login to the 882 site, which uses FBA, I experience the same problem. If I open an Office document, the appropriate Office application opens, and asks me for my credentials, by showing me a dialog window with the sign in page loaded. If I choose to save the file, then I am not prompted to login, and the file saves to a local folder.
I can't expect my users that are off site to login again everytime they open an Office document, like Work, Excel, Powerpoint, etc. I have tried numerous fixes, including disabling client integration, changing the browser handling mode (strict/permissive), changing internet explorer settings (for integrated windows authentication), changing the integrated windows authentication site to use basic authentication, even hacking the page using jquery to call the sharepoint javascript function that execute the "download a copy" function. None of them work: when choosing to "open" the Office document in the browser, the user has to login again, or just close the dialog window without logging in (as long as client integration for the zone is turned off).
I'm looking to get this accomplished using windows authentication or forms based authentication.
Help!
I found this answer in a similar post which seemed to fix the problem for me when I tested it. The gist of it is you need to deny the HTTP Verbs OPTIONS and PROPFIND in IIS. Having said this, I'm not an IIS guru and am not exactly sure what this means or what else it might affect. Can anyone else shed some light on this?
A bit of background, I'm using SharePoint 2010, on an FBA site.
You have the standard three use cases:
Employee intranet access
Employee remote access
Partner remote access
Employee intranet access
This normally always works out of the box, and it looks like it is working for you.
Employee remote access
The only way that i have seen this work (and i have tried many ways) is to get TMG or ISA. Basically ISA is setup in FORMS auth with SSL, it captures the auth details, and then passes them to the sharepoint server. (and other servers if you have them eg OWA for sharepoint mail web parts)
If you select the "Is private computer" option on the ISA login screen, then Office documents share the auth cookie and don't prompt for another login. I had so many problems, but as soon as i installed TMG, they all went away. I would not recommend any other approach now.
The added bonus of this method, is that remote employees are treated as the same account as the intranet user. The way you are setup with a seperate web application, means that they will be different accounts, so things like [checkout/modifiedby/createdby/personalisation] will be different accounts (though they look the same)
Partner remote access
This may never ever work on some clients (especially Vista), as IE needs to share the authentication with Office
If this is sharepoint 2010, try this.
Get-SPSecurityTokenServiceConfig
Look at your UseSessionCookies value in the output. If True, apply the powershell below.
$sts = Get-SPSecurityTokenServiceConfig
$sts.UseSessionCookies = $false
$sts.Update()
If UseSessionCookies is true, you will have to login to any docs u want to download...
After I log into my sharepoint website, I have to login everytime I access a document from the library. Is there a way to fix this?
Thanks
User Level:
If your SharePoint site always prompts for username/password on accessing it you can set your browser to not prompt
In Internet Explorer, go to Tools
Click Internet Options
add your site URL to Internet Explorers "Local Intranet Sites" section.
Open Security tab
Click Custom Level button
Scroll down to this screen and select "Automatic logon with current username and password" radio button
Click OK.
Administrator Level:
you can add your site's internal zone URL in Alternate Access Mappings section on Central Administration>Operations site, The SharePoint server always does not prompt for username/password and you can enjoy.
When using Windows Vista or Windows 7 the office tools (e.g. Word) do not look at the Local Intranet list of Internet Explorer. But they look at the following registry location:
HKEY__LOCAL__MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters\AuthForwardServerList
If your sharepoint site is located at share.myserver.com you can set the above registry entry to *.myserver.com (including the *) so that all addresses ending with myserver.com are trusted by the office applications. This will prevent the login popup box from appearing.
For more info see this microsoft article. It solved the problem for me.
Add the SharePoint site to your trusted sites or local intranet in Internet Options.
This is to do with the way Word does the request for a file It sends an anonymous request first. What solves this is setting the session cookie to be valid for a year.
Are you using AD for the Authentication ?
Are you browsing the site from same network where it is hosted or on a Different N/W ?
If in the Same new work "Add the SharePoint site to your trusted sites or local intranet in Internet Options" and in the Trusted Sites Security Custom Level , User Authentication Section select the Option Automatically Login with the Current User Name and Password.
If you are browsing from Different n/w its bit tough to get it .
I experience this every day. My local machine is on a different domain to the SharePoint server so I have to log in every time I access SharePoint with a different application. This includes IE, Word, InfoPath, etc...
There is no way I've found to avoid it as it's simply part of using Windows authentication. Saving your password can help but still shows a dialog.
There are quite a few things that could cause this and you don't give much detail on your setup in the Q to give you an answer but...
The most comprehensive article I've found for troubleshooting this is
Unwanted Authentication Prompts
This issue is familiar to me and I've previously used the upvoted solution to the problem. However, recently I discovered that using Google Chrome rather than Internet Explorer makes this problem go away!
Solution: Use Chrome.
Switching to Basic Authentication will resolve this issue at a cost of passing credentials in clear text.
Before I begin asking this question I will have to warn you that I know next to nothing about SharePoint and I'm basically learning as I go along.
Here's where I am right now:
I have a virtual pc with an instance of SharePoint and windows server 2003 running on it
I have managed to get a network adaptor set up so I can access the SharePoint instance via a web browser in the host.
I have created and published a InfoPath form to the SharePoint instance and I can view the form in a browser from my host machine.
So far everything is great, the only issue is that in order to view the SharePoint Instance or InfoPaths form in the browser I have to first login as the virtual PCs administrator. Now what I want to do is view the same InfoPath form in a mobile device.
Here's what I have done next:
On my host machine I created a Windows CE 3.5 application
in which I added a web browser control and pointed it at the hosted InfoPath form on the SharePoint instance.
Now when I run the application in a mobile emulator I get a connection error, though I do not get this error if I point the control to google, or some other site.
I now have the distinct feeling that the reason for this is that as I mentioned to access the form I needed to login using windows authentication. I tried changing the web application in IIS to allow anonymous access and not require windows authentication. While this worked the SharePoint site stated "Not authorized" so now I gather that SharePoint builds on top of windows authentication to control access to its functionality.
So finally, after all that here's my actual questions:
How do I grant access in SharePoint to specific bits of functionality for specific windows users?
For a mobile device that is not a user on the same network as the SharePoint instance how do I give it access to view the InfoPath form?
I know my questions are a little rambled but one bit issue I have with all this is I am really not sure what to ask, or how to word it. Hopefully someone has grasped what I am trying to do and help out.
To summarize: I basically want to have an emulated mobile device (on the host) access an InfoPath form served by SharePoint/Forms Server on a virtual PC image.
When you want to change authentication to SharePoint never do so by changing settings in IIS directly but go to Central Administration, Application Management, Authentication Providers. There you can set it up to use basic authentication, Forms Auth or Anonymous access.. whatever works for you.
Forms Services may have further challenges but this should at least get you a login.