Pages stop loading or return to login page when trying to access different parts of 1Password Teams

jpartain89

When I am logged into my 1password site, it allows me to go through, maybe, 2 to 4 link presses before something freaks out and the pages stop changing. The URL will change maybe once, but the page itself doesn't, and I either have to reload which forces a re login or it automatically shows the login page. And after the login page auto loads, it won't sign back in without a manual reload.

This is either Safari or Chrome on OS X 10.11.3 beta 3. I will be updating to beta 4 here shortly but I don't think that'll change anything.

---

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: 10.11.3
Sync Type: Not Provided

rob

Hi, @jpartain89.

Thanks for the report! If this is reproducible, could you do it again and let me know what link you pressed when the URL changes but the page doesn't? It sounds like you're running into an error that we should be handling better. If you open the JavaScript Console (Command-Shift-C in Chrome), you'll probably see an error there that we aren't catching. If so, a screenshot of that error would be helpful in figuring out the problem.

I just fixed an issue earlier today that might have been this issue, and we'll hopefully have the fix deployed to the live site tomorrow. If there's another one, though, we definitely want to know about it.

Thanks again!

jpartain89

Hi @rob

It looks like is specifically the "Invitations" section of the Admin Panel that makes it freak out.

Not sure if anything in that shot is security sensitive in any way... So feel free to remove it if it is!

Jacob

@jpartain89 Ah, that's familiar. We just fixed a bug that stopped the Invitations tab from working if there were no allowed domains in the list. It should be fixed in production in the next few days. Sorry for the trouble!

ref: B5-1167

jpartain89

Awesome @penderworth, thanks so much for the quick update! Hopefully these types of kinks can be ironed out sooner rather than later.

Just one quick request that might not be so quick to implement.... Why is the full web experience not also duplicated in what could possibly be a more unified experience?

Just wanted to see what the thought processes or future possibilities were.

Jacob

@jpartain89 No problem at all. When you say duplicated, do you mean the same design as the desktop apps? We're working on making them as consistent as possible. :)

rob

@jpartain89, we updated the site today with the fix for the Invitations page. I'm sorry it took so long. We're working on a bunch of behind-the-scenes things and it's been holding up web site deployments lately.

I too am curious what you mean by the web experience being duplicated. Could you clarify that question for me?

jpartain89

Hey @penderworth and @rob, thanks to both of you for the quick responses, and @rob.... That timeframe is still much faster than what you could expect from most any other company... Period! Heck, the fact that two of you are responding to my one post, HANDS DOWN, and repeatedly proves to me that you guys truly know how to run an amazing company...

Anyways, what I meant for the Admin Tools is, at a minimum, having those options - the setup, invite, management, all of it - in the desktop and maybe even mobile versions of your apps.

We're already in the installed apps for everything else as it is, right? And thats where all of your prior infrastructure for encryption and basic syncing capabilities are built in and are tried and proven. Personally, I think I would've started with the apps and forgone the web based admin pages all together to start. Unless there was specific user requests for the setup to be managed that way?

Jacob

@jpartain89 We try to be as on-top-of-things as we can, being AgileBits. ;)

Anyways, what I meant for the Admin Tools is, at a minimum, having those options - the setup, invite, management, all of it - in the desktop and maybe even mobile versions of your apps.

Ah, I totally see what you mean. We've actually not had that much feedback about this, surprisingly. I personally think it makes more sense to keep things in the web interface, but I can see where you're coming from too. The thing is, when you look at services like Slack, Square, GitHub, and even something larger like Spotify, the administrative and management duties are always performed in the browser. The apps do have some account settings for quick access, but to invite people you always need to use the backend on their website. We may add some of those quick access features, too, and we will likely add some links to the web interface in the future for more administrative tasks.

Also, it's good to note that having the Teams Admin Console on the web means that we can iterate very quickly on it and push hot fixes if necessary. Apps require build time. Native behavior is nice, but not necessary for something like the Admin Console, and having things in the browser is faster for you as the user as well. :)

Hopefully that gives you a better idea of our thinking here. I'm glad you're loving the native apps, and we are as well. None of us could live without them. They're just not quite right for admin things.