Oh boy!

This is the first public beta of Alliance Auth v2. It's a big change.

What's New

Because CCP is depreciating API keys soon:tm: the goal of v2 is to replace them with SSO tokens. That meant the logic attaching characters to user accounts required an overhaul.

User registration has been revamped. Users now register using SSO. Usernames and passwords are no longer accepted. Emails are validated.

Deployment has changed significantly. Instead of cloning the source from github and running directly, auth is now installed like a standard python package and used to create custom django projects.

Python2 is dead. Auth only works with Python3.4 or newer.

Django 2.0 was released and is supported.

There are a ton of smaller changes I don't feel like mentioning here. All changes are listed in the v2 project.

Documentation has been updated and is available on readthedocs.

Installing

To install v2 a slight modification to the docs is necessary. The auth package hasn't yet been published on pypi, so instead of pip install allianceauth you'll need to pip install git+https://github.com/allianceauth/allianceauth@v2.0b1

Upgrading

Before proceeding ensure you're on v1.15 or newer.

There's no way to upgrade your code from v1 to v2 because of the new deployment method. However your database can be migrated to v2 automatically. Follow the install instructions for deploying v2 and when defining the database in your project's settings file, point at a copy of your old v1 database to migrate it.

Issues

The goal of the beta is to iron out any issues we've missed. Please reach out to us on gitter or open an issue here (being sure to mention it's regarding v2.0b1).