Our vBulletin migration is complete.
Welcome vBulletin users! All content and user information from the Micro Focus Forums (vBulletin) site has been migrated to this site. READ MORE.
Respected Contributor.. Ravi4it Respected Contributor..
Respected Contributor..
359 views

ALM octane login issue

Hi,

We have deployed ALM octane 12.60 CP8 with MS SQL Server 2014 and Elastic search 5.6.5

I am getting message "server is ready". I am able to launch ALM octane portal (http://servername:8080/ui)., However, i am not able to login to ALM Octane. When i enter the username and password, the portal does not logon.. if i enter wrong password, i get error "Invalid Authentication".

Kindly note, i am able to login from the ALM octane server using localhost. (http://localhost:8080/ui) 

Below are some errors from the logs

Octane.log

2019-01-24 14:46:31 ERROR | failed to get experiment status for 'server_role_experiment', defaulting to off. Error: Parameter SERVER_ROLE_EXPERIMENT_EXPERIMENT does not exist and no descriptor with default value was defined
com.hp.mqm.platform.params.NoDefaultValueParamException: Parameter SERVER_ROLE_EXPERIMENT_EXPERIMENT does not exist and no descriptor with default value was defined
at com.hp.mqm.ps.platformservices.params.ParamsServiceImpl.getParamAsBoolean(ParamsServiceImpl.java:87) ~[mqm-ps-platform-services-impl-12.60.21.96.jar:?]

2019-01-24 14:48:50 WARN | [LOCAL] [Octane] [3.9.1] You configured your member address as host name. Please be aware of that your dns can be spoofed. Make sure that your dns configurations are correct.
2019-01-24 14:48:51 WARN | [server.domain.xxx]:5701 [Octane] [3.9.1] Wrong bind request from [server.domain.xxx]:5701! This node is not the requested endpoint: [server.domain.xxx]:5703
2019-01-24 14:48:57 WARN | Reinitializing server sequencing. This is a valid situation only when needed to delete an existing schema during schema setup.
2019-01-24 14:48:57 INFO | Global server time offset has expired and was recalculated. New offset: 9 millis
2019-01-24 14:48:57 DEBUG | Query execution took: 0 msec
2019-01-24 15:39:56 WARN | [server.domain.xxx]:5701 [Octane] [3.9.1] Wrong bind request from [server.domain.xxx]:5701! This node is not the requested endpoint: [server.domain.xxx]:5703

wrapper.log

2019/01/24 14:55:46 | Not found in 'org.owasp.esapi.resources' directory or file not readable: C:\octane\server\ESAPI.properties
2019/01/24 14:55:46 | Not found in SystemResource Directory/resourceDirectory: .esapi\ESAPI.properties
2019/01/24 14:55:46 | Not found in 'user.home' (C:\windows\system32\config\systemprofile) directory: C:\windows\system32\config\systemprofile\esapi\ESAPI.properties
2019/01/24 14:55:46 | Loading ESAPI.properties via file I/O failed. Exception was: java.io.FileNotFoundException
2019/01/24 14:55:46 | Attempting to load ESAPI.properties via the classpath.
2019/01/24 14:55:46 | SUCCESSFULLY LOADED ESAPI.properties via the CLASSPATH from 'esapi/' using current thread context class loader!
2019/01/24 14:55:46 | Attempting to load validation.properties via file I/O.
2019/01/24 14:55:46 | Attempting to load validation.properties as resource file via file I/O.
2019/01/24 14:55:46 | Not found in 'org.owasp.esapi.resources' directory or file not readable: C:\octane\server\validation.properties
2019/01/24 14:55:46 | Not found in SystemResource Directory/resourceDirectory: .esapi\validation.properties
2019/01/24 14:55:46 | Not found in 'user.home' (C:\windows\system32\config\systemprofile) directory: C:\windows\system32\config\systemprofile\esapi\validation.properties
2019/01/24 14:55:46 | Loading validation.properties via file I/O failed.
2019/01/24 14:55:46 | Attempting to load validation.properties via the classpath.
2019/01/24 14:55:46 | SUCCESSFULLY LOADED validation.properties via the CLASSPATH from 'esapi/' using current thread context class loader!
2019/01/24 14:56:15 | 2019-01-24 14:56:15.059:WARN:oejs.DoSFilter:Scheduler-819347389: Unknkown context for rate tracker RateTracker/10.16.3.154/1

Please advise

Thanks

0 Likes
4 Replies
Ziv_Birer Super Contributor.
Super Contributor.

Re: ALM octane login issue

Hi,

What is the URL of your octane server? 

If you installed octane on public cloud like AWS or AZURE there is some limitation that octane currently have related to possible URLs.

We have a workaround for this issue. I will send it once I see that it is related to your issue.

Regards,

Ziv

0 Likes
Respected Contributor.. Ravi4it Respected Contributor..
Respected Contributor..

Re: ALM octane login issue

Many thanks. Please ignore the previous error details.

Issue:-
While deploying ALM Octane, In Setup.xml, i created a dummy user as Octane administrator.  Now i like to change the username? I see octane user enteries are made in database. How do i change the Octane administrator username and password?

We like to integrate LDAP in ALM Octane. Does the ALM Octane Administrator password requirements should match the ADFS account.

 

0 Likes
Ziv_Birer Super Contributor.
Super Contributor.

Re: ALM octane login issue

Hi,

I will check this and let you know.

Ziv

0 Likes
Highlighted
Ziv_Birer Super Contributor.
Super Contributor.

Re: ALM octane login issue

Hi,

For internal authentication user

User details can be modified by the workspace\sharedspace administrator user via the user settings UI. For a logged in user, its own password can be changed from user profile --> change password.

To switch to LDAP authentication

Octane siteAdmin user should be a real user in the configured LDAP server.

This requires:
1. If the existing siteAdmin user in Octane is not a real LDAP user, it is possible to update setup.xml file with a real LDAP user.. This user will be created in Octane DB on restart.

2. Setting the 'adminDn' field in octane.yml file under the 'ldap' section with the siteAdmin user LDAP dn value
Octane should be restarted after applying these changes..

Regards.,

Ziv

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.