Bug 17867 - RHN does not check to see if a user exists
Summary: RHN does not check to see if a user exists
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: up2date (Show other bugs)
(Show other bugs)
Version: 7.0
Hardware: i586 Linux
medium
medium
Target Milestone: ---
Assignee: Preston Brown
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-09-26 19:05 UTC by Panic
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-09-26 19:05:39 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Panic 2000-09-26 19:05:37 UTC 
Guys,

There is no selection for RHN client under component selection, so I used
up2date.

The RHN registration tool does not check with the website to see if a user
exists.  Therefore, it is possible for someone to submit a username that
already exists (but is not their own). (rhnreg.py, gui.py?)

If an already existing user name is used, the user is blocked from
accessing their RHN account -- they get the error:

Username or password is incorrect

when they attempt to log into the web server to access their RHN pages
(www.redhat.com/network).  This error is true, of course, but there is no
indication that the user account already exists (and doesn't belong to them).

Panic
Comment 1 Panic 2000-09-26 19:32:07 UTC 
This is wrong -- my fault, it must've been something about the "panic" account
that I tried to use.  I'll close it out.
Note You need to log in before you can comment on or make changes to this bug.