I encountered this situation recently. I had consolidated two logins. One was for 2012, the other for 2011. It’s better to reuse your login from previous years instead of creating a new one each year. Why? It lets the program committee see what you’ve submitted in previous years. They can see your previous acceptances/rejections. That is very useful, both in a negative and a positive fashion.
The error upon login was:
You are lacking permissions to login to the submission system. The most likely cause for this is your account has not yet been activated.
The solution: add an entry to the auth.account_role table.
I discovered this by poking around via psql. I found this interesting difference.
FYI, the person_id values represent:
- 1 – me
- 160 – the person who could not login
- 187 – a person who could login
pentabarf_bsdcan=# select * from auth.account_role where account_id in ( select account_id from auth.account where person_id in (1, 160)); account_id | role ------------+----------- 49 | admin 49 | developer (2 rows)
In the above case, the other person has no entries.
pentabarf_bsdcan=# select * from auth.account_role where account_id in ( select account_id from auth.account where person_id in (1, 187));
account_id | role
49 | admin
49 | developer
177 | submitter
But as you can see here, the person who can log in has a ‘submitter’ row.
The solution is to add in the missing row:
pentabarf_bsdcan=# insert into auth.account_role values (186, ‘submitter’);
INSERT 0 1