Bug 17867 – RHN does not check to see if a user exists

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

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

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	up2date (Show other bugs)
Sub Component:
Version:	7.0
Hardware:	i586 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Preston Brown
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-09-26 15:05 EDT by Panic
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-09-26 15:05:39 EDT
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.)

Groups: None (edit)

Description Panic 2000-09-26 15:05:37 EDT

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 15:32:07 EDT

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.