iOS – Remembering Passwords for HTTP Authenticated Sites

authenticationiosmobile-safaripassword

There's a page I frequently access on my iPhone that's protected by HTTP authentication, and I'm finding it annoying having to type in my username and password every time I want to access it. I tried saving the logged-in page as a home screen icon, but I'm still prompted every time. There isn't option to save my password when I'm logging in, and I can't find one in the settings either.

Is this possible?

^{example authentication screen to show what I'm referring to}

Best Answer

It seems that Safari on iOS doesn't support this natively. You have a couple options:

Workaround:

If you're not too worried about security, you can embed the username and password in the link itself, and bookmark that:

http://username:password@hostname.com/...

(Also of note: it sounds like iOS may pop up a warning when you visit a link that includes a username and password.)

Alternative:

There is another browser called Atomic Web Browser [App Store link] that can autofill HTTP authentication, among many other neat features.

Related Solutions

Keychain won’t remember the SSH password when connecting to server

There is a lot of conflicting information I've read whenever I look up information on using ssh-agent (passphrase saving/reusing process) under Mac OS X. Most resources seem to suggest that simply issuing ssh-add -K will let you store your passphrase, and will automatically configure OS X to launch ssh-agent automatically and load your stored passphrase.

Note: Running ssh-add -K will only work if you have your private key file in one of the common locations, those locations being limited to: ~/.ssh/id_rsa, ~/.ssh/id_dsa, ~/.ssh/identity. If the file is located anywhere else you should specify that path after the -K in the command above.

The reason you are getting the key file passphrase dialog when connecting to the second (key-less) server is likely because the default configuration of SSH servers is to use public key authentication first, and 'keyboard interactive' authentication second.

Because you have a public key with a standard name/location (~/.ssh/id_rsa), your OpenSSH client helpfully submits the private key in order to allow the server to match it against an allowed authorized_keys file.

There are a small handful of ways to prevent this, the easiest two being to pass a flag on the command line, or add it as a permanent configuration item in your ~/.ssh/config file.

When connecting to the secondary/key-less server, you can add -o "PubkeyAuthentication=no" when connecting. Something like ssh -o "PubkeyAuthentication=no" me@devserver2.
Open up ~/.ssh/config in your favorite text editor, create it first if you must, and enter the following:
```
Host devserver2  
    User me  
    PubkeyAuthentication no
```

Now, if you simply type ssh devserver2 the username and pubkey configuration will be read in and used, and you should be prompted for your password and nothing else.

(Note: Replace devserver2 with the actual hostname of the server. Alternatively, pick a nice hostname, such as devserver2, and add a property between User and PubkeyAuthentication called 'Hostname' and put the name or IP address of the server there. Afterwards, you actually can simply type 'ssh devserver2' and all the configuration properties will work their respective magic.)

MacOS – Web-based wireless login: remember password

The special window is an instance of Safari, just without all the navigation bits.

Why don't you try copy-pasting the URL of the login screen to your browser, typing in your password, and telling safari you want to save it when it asks?