Bug 51417 - Logging in through the store doesn't appear to work
Logging in through the store doesn't appear to work
Status: CLOSED CURRENTRELEASE
Product: Red Hat Web Site
Classification: Red Hat
Component: Store (Show other bugs)
current
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Web Development
Web Development
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-08-10 08:20 EDT by Jay Turner
Modified: 2015-01-07 18:50 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-08-10 08:23:51 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)

  None (edit)
Description Jay Turner 2001-08-10 08:20:13 EDT
Description of Problem:
Logging into the store through the /apps/checkout pages doesn't appear to
work.  I get logged in (it appears) but the buttons don't change so that I
can continue with the checkout process.

How Reproducible:
Always

Steps to Reproduce:
1. Pull up http://www.webqa.redhat.com
2. Click on Store, then place something in the cart
3. Click the Checkout button to start that process
4. When prompted to log in, do so as rhn7_mocha

Actual Results:
Screen will refresh and we have a logout button, but the other button on
the page still says "Register and Continue Checkout" as opposed to the
option to continue with secure checkout or perform an insecure checkout.

Expected Results:
Should be able to select secure or insecure checkout and then complete the
process.

Additional Information:
Comment 1 Jay Turner 2001-08-10 08:23:45 EDT
Note that I am able to get the correct buttons if I log in through the
/apps/user/login.html page, then continue to the store.
Comment 2 Jay Turner 2001-08-10 15:45:39 EDT
This appears to be the result of a change from last night as well.  That change
has been backed out and now this login process is working.  Closing this issue out.

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