Bug 1013903 - In ER4, the installer does not allow for the user to change the Governance username - hardcoded as "admin"
Summary: In ER4, the installer does not allow for the user to change the Governance us...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: Installer
Version: 6.0.0 GA
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ER7
: 6.0.0
Assignee: Thomas Hauser
QA Contact: Len DiMaggio
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-01 02:44 UTC by Len DiMaggio
Modified: 2014-02-06 15:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-06 15:26:46 UTC
Type: Bug


Attachments (Terms of Use)
Screenshot (109.22 KB, image/png)
2013-10-01 02:45 UTC, Len DiMaggio
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1011060 0 urgent CLOSED Installer: If the user customizes the "overlord credentials" section of the installer, sramp seeding will fail 2021-02-22 00:41:40 UTC

Internal Links: 1011060

Description Len DiMaggio 2013-10-01 02:44:41 UTC
Description of problem:

See the attached screenshot - the install allows the user to change the password, but not the username.

Version-Release number of selected component (if applicable):
ER4

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Len DiMaggio 2013-10-01 02:45:39 UTC
Created attachment 805676 [details]
Screenshot

Comment 2 Thomas Hauser 2013-10-01 13:26:58 UTC
It was decided to not allow the username to be changed for beta, as per discussion with Eric Wittman. This bug will be resolved when the ability to change the user is added.

Comment 3 Thomas Hauser 2013-10-21 20:37:44 UTC
This is resolved in post-beta builds.

Comment 4 Jiri Sedlacek 2013-12-12 13:17:42 UTC
verified in ER7, there is a possibility to choose username for SSO


Note You need to log in before you can comment on or make changes to this bug.