Bug 131519
Summary: | Allow Satellite users to create their own accounts | ||
---|---|---|---|
Product: | Red Hat Satellite 5 | Reporter: | Matt Domsch <matt_domsch> |
Component: | Server | Assignee: | Mike McCune <mmccune> |
Status: | CLOSED WONTFIX | QA Contact: | Red Hat Satellite QA List <satqe-list> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | nhruby, wwlinuxengineering |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-10-29 14:23:24 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Matt Domsch
2004-09-01 20:44:38 UTC
mass reassign to mmccune In addition, if the satellite is using PAM authentication, that should be a globally enabled item, and then should not ask for a password at account creation time, as the password won't actually be used thereafter - the PAM-checked password will be. Note: RHN Satellite 5.0.0 beta still has this problem, >2 years after my initial request. giving up on this request for now. Maybe it'll reappear in spacewalk. |