Skip to main content
By

An introduction to SessionBox - what's this and why we are doing it?

Develop web applications, test new features, log out of personal Gmail, log in with a test account, then repeat to check with another one. Probably use different browsers, or Chrome profiles, so that I won't need to re-login for every test. Quite a pain.

Mainly this continuous context switching and re-login (mostly even with 2FA) was the reason why we started thinking about finding a solution, that could persist different contexts in one single browser, using different tabs. And that's exactly what SessionBox does.

Handle both Personal and Work related sessions in the same browser window. Eg. multiple Google / Gmail accounts can be easily used at the same time.

Our pain of dealing with continuous user context switching lead to a hobby project, that has already reached over 38.000 downloads, and more than 25.000 monthly active users. This was the number at which we thought this might lead somewhere, so let's try concentrating a bit more on this app, and bring more and better features that can be based on the technology and basic ideas behind SessionBox.

Open any site easily in a SessionBox-managed session through the context menu or the extension itself.


Therefore we are not only trying to answer all user requests, deliver new features - we have dozens of cool ideas :) -, we are also starting this blog, to share you all improvements, show you how we use SessionBox in our everyday enterprise developer life, and what the underlying technology and security solution is - it will worth checking!

Quick way to add a session to SessionBox. Just be sure to open the session through either the context menu or the extension, so that you will get this popup, to store your session in SB. Use the More Options / Group here, that's very handy!

We are also happy to hear any feedback, or ideas from you, so let us know if you have anything on your mind at support@sessionbox.io.

You can reach the Chrome extension through the Chrome store and check out our welcome site at https://sessionbox.io/.

Be prepared to hear more from us!
-
The SessionBox team.
Labels:

Comments

Post a Comment

Popular posts from this blog

Share access without giving away your password with SessionBox

By
Share your sessions Did you ever wish to pass over one of your accounts to a friend of yours? Or is your company using shared accounts for your daily activities? Well, there are some solutions, but all of those include sending over your password to the other party - sometimes client side code tries to hide this fact, but any savvy user can easily get around that. With our latest release (1.0.35) we have added a new feature, called Session sharing. With this brand new possibility we provide a new way of sharing your accounts, without sharing the password itself. Moreover, you can limit the timespan of the sharing itself, so if you just want to show something to your friends, you can give them access for an hour, then they won't be able to access your account again. How to start sharing? Open up the context menu for the session you wish to share. You can see a new item here, called "Share..." Select the domains you want to share. Browsing around on t...
1 comment
Read more

Be secure with SessionBox

By
A large percentage of web based attacks can be avoided with careful planning and implementation of the website's code. However, a large portion of attacks directly target the user's browser, where the protection imprinted into the server side architecture is many times not enough. This is the area where SessionBox helps you. A number of different attack methods base their attack vector on the fact, that users are already logged into other websites. Let's take an example. You are probably logged into Facebook. When you visit a site - let's call it example.com - this site runs many scripts inside your browser. Where you have active sessions for Facebook.com. This means that example.com can for example send requests to Facebook.com - where you are already authenticated - and make actions on your behalf. Moreover, example.com might be a trusted site, but they can also be attacked, and if they are not prepared against XSS attacks, a savvy hacker can inject their scrip...
Post a Comment
Read more