Logging in as USER@drupal.org, creates a second account which appears to inherit the same password, yet distinct profile and tracker info as it has a separate UID from your primary account.

This issue is further compounded when the user then participates in the forums / issue queue unknowingly using both accounts. *As I have unwittingly done

Doing a quick user search, this would appear to be a mistake made by many other members as well http://drupal.org/search/user/%40drupal.org.

Comments

gerhard killesreiter’s picture

gerhard killesreiter commented
Project: Drupal.org infrastructure » Drupal core
Version: » 5.x-dev
Component: Other » drupal.module

IMO this is a Drupal bug.

maartenvg’s picture

maartenvg commented
Project: Drupal core » Drupal.org infrastructure
Version: 5.x-dev »
Component: drupal.module » Other

In Drupal (the software) this is by design: someone using the external login should get their own uid to differentiate between local users.

This is not the case for drupal.org (the website), where there is no difference between local users and username@drupal.org users.

But please Gerhard, please elaborate on why this is a general problem.

maartenvg’s picture

maartenvg commented
Project: Drupal.org infrastructure » Drupal core
Version: » 5.x-dev
Component: Other » drupal.module

Sorry, didn't notice you were an infrastructure-maintainer.

catch’s picture

catch
he/him
Primary language English
commented

drupal.module allows you to specify many different sites that people can login from, so this isn't specific to Drupal.org. Also drupal.module is now site_network module in D6, so this probably needs fixing in core first then forward-porting.

bradweikel’s picture

bradweikel commented

This doesn't appear to be happening on d.o anymore. Presumably the upgrade to D6 took care of it. I'd suggest closing this out, but someone should probably double check to be sure my test was accurate.

dpearcefl’s picture

dpearcefl commented
Status: Active » Closed (won't fix)

Considering the lack of activity on this issue and that Drupal v5 is no longer supported by fixes or patches, I am going to close this ticket. If this issue still exists and you want to continue to ask for technical support, please reopen and update this ticket.