Bug 693591 - Activation email from Zanata has invalid URL.
Activation email from Zanata has invalid URL.
Product: Zanata
Classification: Community
Component: Authentication-Internal (Show other bugs)
All Linux
high Severity high
: ---
: ---
Assigned To: zanata-dev-internal
Ding-Yi Chen
Depends On:
  Show dependency treegraph
Reported: 2011-04-04 21:41 EDT by Kenichi Takemura
Modified: 2014-08-04 18:03 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-04-04 22:40:32 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Kenichi Takemura 2011-04-04 21:41:27 EDT
Description of problem:

Start Zanata specifying hostname (run.sh -b hostname)
so that user can access to zanata via http://hostname:8080/zanata.

When registering a user, 'Zanata Account Activation' email contain a URL which is http://localhost:8080/... where the operated user cannot access.

Dear Kenichi,

Please click on the following link to activate your account:


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

How reproducible:

Steps to Reproduce:
1. Start Zanata; $JBOSS_HOME/bin/run.sh -b hostname
2. Register a user from Zanata
3. Check email for Account Activation
Actual results:
Clicking on the provided link to activate the account is invalid url.

Expected results:
The URL should point to Zanata host.

Additional info:
Comment 1 Kenichi Takemura 2011-04-04 21:50:07 EDT
Additional info.

Zanata host is configured to get address from dhcp server.
It `hostname` returns

$ hostname
Comment 2 Sean Flanigan 2011-04-04 21:55:25 EDT
Please see http://code.google.com/p/flies/wiki/InstallationGuide#Configuration

Jacquelynn, can you please make sure the initial configuration steps are easy to find when you develop the installation/admin book?
Comment 3 Kenichi Takemura 2011-04-04 22:40:32 EDT
Thanks for your support.

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