We’ve made some changes to the login system for the Account Manager that are now live on our production Account Manager.  I’d like to outline what those changes are and the reasons we made them.

What the changes are

• The next time you log in to the Account Manager (or go to the Account Manager if you had your account set to “Remember Me”), you will be prompted to migrate your password.
• During this migration you will be prompted to enter your current password, followed by a new password two times.
• You will also be prompted to enter a Security Question and a Security Question Answer.  The question is a freeform text field that you can put whatever question or other information you like.  This “question” will be given to you as a prompt during the “Forgot Password” procedure.  The answer is the data you will be prompted to enter as the answer to your question.

Why we are making these changes

There are a number of reasons why these changes are being put into place.  First of all, we are using a new method of storing user passwords that provides additional security and utilizes a different hashing mechanism than we used before.  Some additional reasons for this change are:

• We are consolidating user records in our system.  When this process is complete, customer admin accounts and end user accounts will be consolidated into one system to allow for consistency across our systems.
• We will be adding in functionality to allow customers to designate additional administrators.  These additional administrator accounts can be set up as full-fledged account administrators or can be given access to various areas of the Account Manager, including fine grain control down to the server and/or domain level.
• We will be consolidating the quarantine system into the Account Manager, making one place where users log in to see their quarantine and manage their account.  Since we released custom branding options for our customers, the need for a separate quarantine site that is under a different brand has diminished.

At this time, the only changes that have been made have been to migrate existing customer admin accounts to the new user system and add the additional security measures surrounding logins to the site.  As we release additional changes we will post about them here on the blog.

Please comment here or contact support@purity.net if you have any questions or issues with the new system.

The first version of custom branding on quarantine digests is done.  This version incorporates the custom logo, URL, and from email address, but uses a “plain” grey color scheme.

We’ll be making some changes to the branding in the next couple of weeks to replace the custom CSS that we currently have with specific color selections.  This will allow us to use those color selections to customize the HTML version of the quarantine digest and to generate custom CSS for the website on the fly.  It will also be easier to modify than the CSS for those that are not familiar with CSS.

We’ve enabled the new quarantine branding system for our users.  To custom brand your quarantine, log in to the Account Manager and click the link to enable custom branding.  Once you’ve done that, edit your branding settings and input your custom URL, “from” email address, custom CSS, and upload your logo.

A few notes:

• Custom URL: You must DNS this hostname.domain.com to point to the appropriate IP address.  The IP address is listed on the branding screen
• Custom CSS: The default CSS will be entered when you first enable branding.  Feel free to modify as necessary.
• Quarantine Digests are not branded yet.  We should have this finished in the next couple of days.  I’ll post here when they’ve been updated.

Please note that branding is NOT restricted to your domains in any way.  In other words, the “face” of the site is updated with your branding but the internal workings of the site haven’t changed.  All Quarantine users can log in to the site, regardless of the “branded” url they use.

Please let us know if you have any questions.  Please remember that this is still sort of a “beta” feature, so there may be some bugs.  I haven’t found any in my testing, but you may come across some.  If so, please let us know.