Bee.

Security

Bee communicates solely with your designated server.

No intermediary servers are used. Bee smartly caches, polls and fetches deltas directly via your server’s API.

Your Mac is the only computer connecting to your server.


Credentials

When you enter your authentication credentials in Bee, they are securely stored in your Mac’s Keychain locally.

Each service that Bee supports has different requirements for authentication due to differing APIs.

JIRA

There are 2 ways you can authenticate with JIRA:

  1. Username and password directly with a managed cookie-based session

    Bee stores your username and password securely in your Mac’s Keychain. Bee uses the JIRA REST API to maintain a cookie-based session (similar to your web browser). Your session is automatically managed by Bee and renewed whenever needed, transparently.

  2. Web flow

    Bee opens a web browser at your login page. After you authenticate, Bee captures the JIRA authentication cookies and stores them to use in subsequent API calls. Since Bee does not have access to your credentials - it will occasionally ask you to re-authenticate when your session expires.

GitHub

Bee retrieves an OAuth token from GitHub when it first authenticates with your server and then stores this securely in your Mac’s Keychain. Your password is not stored.

Manuscript/FogBugz

Upon first authenticating, Bee retrieves a unique token and then stores this securely in your Mac’s Keychain. Your password is not stored.