Bug 1003000 - [RFE] after installation http://<fqdn>/ is not redirected to http://<fqdn>/sam
Summary: [RFE] after installation http://<fqdn>/ is not redirected to http://<fqdn>/sam
Keywords:
Status: CLOSED DUPLICATE of bug 805265
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-30 12:51 UTC by Jan Hutař
Modified: 2013-08-30 16:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-30 16:10:27 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Jan Hutař 2013-08-30 12:51:37 UTC
Description of problem:
I have just installed SAM 1.3 Snap4, configured it and the attempted to access it's webUI. I have failed because I have not added ".../sam" to the URL.


Version-Release number of selected component (if applicable):
katello-headpin-all-1.4.3-11.el6sam_splice.noarch


How reproducible:
always


Steps to Reproduce:
1. # yum install -y katello-headpin-all
2. # katello-configure --deployment=sam --user-pass=admin
3. Direct your browser to http://<fqdn>


Actual results:
Default Apache page is displayed


Expected results:
You should be redirected to https://<fqdn>/sam/

Comment 1 Tom McKay 2013-08-30 13:08:31 UTC
This is expected behavior: The suffix /sam must be included.

Comment 2 Jan Hutař 2013-08-30 15:39:43 UTC
As I do not consider this user friendly, would it be at least possible to get katello-configure print as a last line something like:

[...]
Now SAM is prepared for you on: https://<fqdn>/sam

? Thanks in advance.

Comment 3 sthirugn@redhat.com 2013-08-30 15:43:13 UTC
this needs a fix in katello. Moving the bug back to Satellite 6

Comment 4 sthirugn@redhat.com 2013-08-30 16:10:27 UTC
@Jan: We have a bug 805265 already open for your request in Comment 2. Thank you!

*** This bug has been marked as a duplicate of bug 805265 ***


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