Bookmarklet access code

milke

<div class="IPBDescription">Typing bookmarklet access code every time</div>I've done all syncing between 1Password for Mac and 1Password (Pro) for iPad. Since I want to use bookmarklet, I've also created one, entered required access code, synced between Safari and Mobile Safari etc.



Everything works like a charm, but there is one annoying thing. Perhaps I'm just missing something. Am I really required to type in the "Access Code" every time I want to use 1Password Logins bookmarklet on Mobile Safari?? I tried different security settings in the main application 1Password Pro for iPad, but that doesn't seem to change this behaviour.



Is there any way not to enter "Access code" every time, at least in a single Safari session, or before the 1Password auto-lock feature kicks in?

brenty

[quote name='milke' timestamp='1312210740' post='35655']

I've done all syncing between 1Password for Mac and 1Password (Pro) for iPad. Since I want to use bookmarklet, I've also created one, entered required access code, synced between Safari and Mobile Safari etc.



Everything works like a charm, but there is one annoying thing. Perhaps I'm just missing something. Am I really required to type in the "Access Code" every time I want to use 1Password Logins bookmarklet on Mobile Safari?? I tried different security settings in the main application 1Password Pro for iPad, but that doesn't seem to change this behaviour.



Is there any way not to enter "Access code" every time, at least in a single Safari session, or before the 1Password auto-lock feature kicks in?

[/quote]



Welcome to the forums, milke! <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/smile.gif' class='bbc_emoticon' alt=':)' />



Unfortunately, this is not possible, since there is no way for the 1Password app to communicate with the bookmarklet in Safari. Essentially, the bookmarkets are self-containted mini-1Passwords with a single Login item, so they have to be authenticated individually. There is just no way to save state. It may be possible in the future as iOS and Mobile Safari mature and become more robust, but only time will tell.