tracker issue : CF-4126507

select a category, or use search below
(searches all categories and all time range)
Title:

Invalid Login For API Manager After Successful Installation

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Travis Walters / Travis Walters (Travis Walters)

Created: 03/09/2016

Components: API Manager, Installer

Versions: 2016

Failure Type:

Found In Build/Fixed In Build: Beta1_v12 /

Priority/Frequency: Normal / Some users will encounter

Locale/System: English / Win All

Vote Count: 0

Problem Description:

Installation issue with API Manager - login does not work after successful installation of API Manager. This occurred after a clean install of Windows 10 Pro and other software.

After consulting with me via Team Viewer, Nimit Sharma was able to reproduce this problem as well.

Problem was discussed in this forum thread:
https://prerelease.adobe.com/project/forum/thread.html?cap=05D198F3B43F49EE950A8643486DF6D4&forid={B099ABD7-4284-4489-B8E2-839E0567F308}&topid={4A8CBC94-5D7F-4985-8DB2-E37BC1C503AB}

Steps to Reproduce:

So I am now trying the API Manager on a clean installation of everything on my Dell Desktop (different computer than before).

- Formatted Hard Drive
- Installed Windows 7 Professional
- Installed Necessary Drivers
- Applied Windows Updates
- Installed Google Chrome
- Upgraded to Windows 10 Pro
- Applied Windows Updates
- Installed VIPRE Internet Security 2016 and Applied Updates

- Installing cf_raijin_beta1_120515_win64
-- Selected 30-Day Trial
-- Selected Server Configuration for Installer Configuration
-- Selected Production Profile
-- Selected All Sub-components
-- Enabled all Servlets
-- Entered Username and Password (same as email)
-- Did not enable remote access for add-on services
-- Installation Path C:\ColdFusion2016
-- Selected Built-in Web Server
-- Did not configure WebSocket Proxy
-- Port 8500
-- Entered Username and Password (same as email)
-- AutoCheck for Server Updates Enabled

Installation Type:
  Server configuration

Licensing:
  30-day trial

Installation Directories:
  Product: C:\ColdFusion2016
  Web Root: C:\ColdFusion2016\cfusion\wwwroot

Server Information:
  Web Server: Built-in web server
  Admin Port: 8500
  ODBC Services: installed
  ColdFusion Server Profile: Production Profile
  ColdFusion Solr Search Services: installed
  ColdFusion Pdfg Search Services: installed
  ColdFusion .NET Integration Services: installed
  Microsoft .NET version: v4.0.30319
  .NET Java Port: 6093
  .NET Client Port: 6094
  RDS: disabled

Disk Space Information (for Installation Target):
  Required: 2,248 MB
  Available: 271,420 MB

-- Finished Configuration Wizard (http://127.0.0.1:8500/CFIDE/administrator/index.cfm)
-- Was able to access ColdFusion Administrator
-- Starting to install ApiManager_beta1_120515_win64 (same as before)

When installing API Manager, I chose to co-exist with an existing ColdFusion installation.

I found one mistake that I was making (and was very positive that it would work after this) but the default installation directory when installing the API Manager was:

C:\coldfusionraijin\cfusion (this is the alpha version and did not realize this before)

I changed the directory to:

C:\ColdFusion2016\cfusion (the beta version of ColdFusion)

As mentioned before, I had some issues with the Alpha version and API Manager where the installation hung on the end and never proceed further.

I then selected port 9000 and for a cluster configuration. I then checked both the data store and analytics server check boxes. Data store port is 6379 and analytics server port is 9200. I am copying and pasting the password (same one from the email I sent you) and using admin as the username.

Product Name:
    APIManager  
?Installation Directory
    ?C:\ColdFusion2016\cfusion  
?Data Store
    ?C:\ColdFusion2016\cfusion/database/datastore  
?Analytics Server
    ?C:\ColdFusion2016\cfusion/database/analytics  
?Portal Port
    ?9000  
?Proxy Port
    ?9100  
?Data Store port
    ?6379  
?Analytics Server Port
    ?9200  
Disk Space Information (for Installation Target): 
    Required: 360.91 MegaBytes     Available: 698,767.22 MegaBytes

...

Congratulations! 
ApiManager has been successfully installed at: C:\ColdFusion2016\cfusion\..\ApiManager.
ApiManager will be up and running as a service. If you chose to install the Data Store or the Analytics server as a part of this installation, they will be up and running as services.
You can log into the ApiManager administrator portal at http://localhost:9000/admin/

Press "Done" to quit the installer.

...

Upon going to http://localhost:9000/admin/login.html, entering the username and password, I still get the invalid username or password error message.

I checked the APIManager_Install_12_09_2015_15_39_16.log installation log and see all success messages.

Actual Result:

Username + Password Login Combination do not work after successful installation of API Manager.

Expected Result:

Login should work.

Any Workarounds:

Nimit Sharma had a workaround for this - something to do with inputting the password directly into a text file and restarting the API Manager service.

Attaching some files that Nimit Sharma wanted - both attachments are the same files just in different formats.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	4126507

External Customer Info:
External Company:  
External Customer Name: Travis Walters
External Customer Email: TWALTERS84@HOTMAIL.COM
External Test Config:  


Bug File Paths:
\\sjshare.corp.adobe.com\Prereleasebugfiles\ColdFusion\12.0\Beta1_v12\4098738\logs.adobe
	 
\\sjshare.corp.adobe.com\Prereleasebugfiles\ColdFusion\12.0\Beta1_v12\4098738\logs.zip

Attachments:

Comments:

Adding BUG AUDIT TRAIL ********action: updated fieldName: Date Closed newValue: 2015-12-15 04:49:04.0 oldValue: Blank oprid: nimsharm recordName: RQ_DEFECT timpestamp: 2015-12-15 12:49:04.0 action: updated fieldName: Closed By newValue: nimsharm oldValue: Blank oprid: nimsharm recordName: RQ_DEFECT timpestamp: 2015-12-15 12:49:04.0 action: updated fieldName: Owner newValue: Blank oldValue: nimsharm oprid: nimsharm recordName: RQ_DEFECT timpestamp: 2015-12-15 12:49:04.0 action: updated fieldName: State newValue: Closed oldValue: Open oprid: nimsharm recordName: RQ_DEFECT timpestamp: 2015-12-15 12:49:04.0 action: updated fieldName: Status newValue: Fixed oldValue: ToTest oprid: nimsharm recordName: RQ_DEFECT timpestamp: 2015-12-15 12:49:04.0 action: updated fieldName: Reason newValue: Blank oldValue: Fixed oprid: nimsharm recordName: RQ_DEFECT timpestamp: 2015-12-15 12:49:04.0 action: updated fieldName: Fixed By newValue: djha oldValue: Blank oprid: djha recordName: RQ_DEFECT timpestamp: 2015-12-14 05:28:51.0 action: updated fieldName: Date Fixed newValue: 2015-12-13 21:28:51.0 oldValue: Blank oprid: djha recordName: RQ_DEFECT timpestamp: 2015-12-14 05:28:51.0 action: updated fieldName: Owner newValue: nimsharm oldValue: djha oprid: djha recordName: RQ_DEFECT timpestamp: 2015-12-14 05:28:51.0 action: updated fieldName: Status newValue: ToTest oldValue: ToFix oprid: djha recordName: RQ_DEFECT timpestamp: 2015-12-14 05:28:51.0 action: updated fieldName: Reason newValue: Fixed oldValue: BugVerified oprid: djha recordName: RQ_DEFECT timpestamp: 2015-12-14 05:28:51.0 action: updated fieldName: Changelist newValue: 296922 oldValue: Blank oprid: djha recordName: RQ_DEFECT timpestamp: 2015-12-14 05:28:51.0 action: updated fieldName: Owner newValue: djha oldValue: sanniset oprid: sanniset recordName: RQ_DEFECT timpestamp: 2015-12-14 05:13:08.0 action: updated fieldName: Dev Assigned newValue: djha oldValue: sanniset oprid: sanniset recordName: RQ_DEFECT timpestamp: 2015-12-14 05:13:08.0 action: updated fieldName: Owner newValue: sanniset oldValue: awdhesh oprid: awdhesh recordName: RQ_DEFECT timpestamp: 2015-12-14 05:03:01.0 action: updated fieldName: Dev Assigned newValue: sanniset oldValue: awdhesh oprid: awdhesh recordName: RQ_DEFECT timpestamp: 2015-12-14 05:03:01.0 action: updated fieldName: Owner newValue: awdhesh oldValue: nimsharm oprid: nimsharm recordName: RQ_DEFECT timpestamp: 2015-12-13 07:47:28.0 action: updated fieldName: Fix By Milestone newValue: Beta2 oldValue: Blank oprid: nimsharm recordName: RQ_DEFECT timpestamp: 2015-12-13 07:47:28.0 action: updated fieldName: Status newValue: ToFix oldValue: Unverified oprid: nimsharm recordName: RQ_DEFECT timpestamp: 2015-12-13 07:47:27.0 action: updated fieldName: Reason newValue: BugVerified oldValue: Blank oprid: nimsharm recordName: RQ_DEFECT timpestamp: 2015-12-13 07:47:27.0 action: updated fieldName: Fix By Product Milestone newValue: Beta2 oldValue: Blank oprid: nimsharm recordName: RQ_DEFECT timpestamp: 2015-12-13 07:47:27.0 action: updated fieldName: Priority newValue: 2 oldValue: 0 oprid: nimsharm recordName: RQ_DEFECT timpestamp: 2015-12-13 07:47:27.0 action: updated fieldName: Found in Phase newValue: Beta oldValue: Blank oprid: nimsharm recordName: RQ_DEFECT timpestamp: 2015-12-13 07:47:27.0 action: updated fieldName: QE Assigned newValue: nimsharm oldValue: inoel oprid: vmannebo recordName: RQ_DEFECT timpestamp: 2015-12-11 05:52:27.0 action: updated fieldName: Owner newValue: nimsharm oldValue: inoel oprid: vmannebo recordName: RQ_DEFECT timpestamp: 2015-12-11 05:52:27.0
Comment by CFwatson U.
3929 | March 09, 2016 02:22:34 AM GMT
Added By:nimsharm Note Added: This issue is fixed. The fix for this issue will be available as part of next APIM drop. Date Added :2015-12-15 12:49:46.0 Added By: PreRelease User User Name:Travis Walters Note Added: Entered Bug. Date Added :2015-12-11 05:30:18.0
Comment by CFwatson U.
3930 | March 09, 2016 02:22:48 AM GMT