Question

I’m using Django registration inside my project on a development server.
When I register a new user, I use EMAIL_BACKEND = ‘django.core.mail.backends.filebased.EmailBackend’ to get the activation link.
When I try to put the activation link into the web browser, I have an error, and the account is not activated.

It is said :

Thank you.
This function is used to generate the key.

def create_profile(self, user):
    """
    Create a ``RegistrationProfile`` for a given
    ``User``, and return the ``RegistrationProfile``.

    The activation key for the ``RegistrationProfile`` will be a
    SHA1 hash, generated from a combination of the ``User``'s
    username and a random salt.

    """
    salt = hashlib.sha1(str(random.random())).hexdigest()[:5]
    username = user.username
    if isinstance(username, unicode):
        username = username.encode('utf-8')
    activation_key = hashlib.sha1(salt+username).hexdigest()
    return self.create(user=user,
                       activation_key=activation_key)

I received that mail. But I use EMAIL_BACKEND’django.core.mail.backends.filebased.EmailBackend’.

I think the problem comes from here. But I can’t test in production server.

I solved the problem actually It’s because I generate the email to send inside a file thanks to the file email backends provided by django for development purpose. Inside this file, when there is a carriage return, it adds an = characters. And this is the case with the link to active the account.

Answer 1

You shouldn’t have a = character in your activation key.

Although sergzach‘s answer will work, I’d be more interested in finding out why that = is there in the first place.

django-registration usually generates the key as follows:

        salt = sha.new(str(random.random())).hexdigest()[:5]
        activation_key = sha.new(salt+user.username).hexdigest()

Where are you generating yours?