Can I make a FileMaker webviewer remember login information...such as the user name and password required to view a gmail account or a google calendar?
I would like the ability to do this with a hosted solution.
Some web services allow to loogin by adding username and password to the url, but this is not the case with google.
On the other hand, I just tried it (OSX 10.9 FMP 10.9) and it works for me. I think it takes local Safari settings, including the saved passwords.
It appears that the behavior has changed. I am running OS 10.10.3. I have the Google user name and password stored in Safari...and Safari loads the Google Account without requiring any input. Unfortunately this information is not passing to FileMaker...requiring it to be entered every time.
Another issue that I am experiencing is that if I start on Gmail and then try to navigate to Google Calendar it launches FireFox (my default browser) and attempts to load the page there instead of in FileMaker.
Sorry, can't help in this case.
Google changes api/setup quite often, so it is unlikely there is an easy solution. feedzone has a solution for integrating google calendar, this could be a better option, provided that your client is happy to pay extra
In theory, tools like "Central Authentication Service" would do this for you via a CAS server and passing a token/certificate. I just posted a question about if someone else has used this tool to authenticate FileMaker users. Otherwise it is up to browsers if they support remembering passwords like Safari does.
I remember a link about a user using cookies in the webviewer. If you could get that to work I would assume you could store user login information in a cookie.
Here is a link on using cookies in webviewer Take a look at the code at the bottom of that link by TANNERELLEN.Re: Web viewer cookie persistence
I have not tested this but maybe it will get you going in the right direction
You can use MBS FileMaker Plugin with functions like WebView.Passwords.Install and WebView.Passwords.Set.
This way you can on Mac at least preload the password into solution and let the user go on the protected page without seeing the password dialog.
Retrieving data ...