Unable to register RM 6.0.6.1 with JTS 6.0.6.1, installed in a distributed topology
![]() I am trying to setup RM and JTS in a distributed topology. Below are the configuration details
JTS-CCM-GC 6.0.6.1 installed on Windows VM1
RM 6.0.6.1 installed on Windows VM2
Using basic user registry and both servers are having same basicUserRegistry file
SSO is enabled on both by adding below lines in server.xml
<webAppSecurity singleSignonEnabled="true"/>
<webAppSecurity ssoDomainNames="windows-vm1-jts-server" />
<ltpa keysFileName="resources/security/ltpa.keys" keysPassword="WebAS" expiration="120" />
"ltpa.keys" files are same on both the VMs
Issue:
During RM application registration step of JTS setup below error is seen:
The webpage at https://windows-vm2-rm:9443/rm/customSetup?embed=true#/steps/1&parent=https%3A%2F%2Fwindows-vm1-jts%3A9443%2Fjts%2FcustomSetup%23%2Fsteps%2F18 might be temporarily down or it may have moved permanently to a new web address.
When I login to RM/admin URI and Advanced Properties, "Pending oAuth Consumer Registration Info" has a value as below:
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:j.0="http://jazz.net/xmlns/foundation/1.0/" > <rdf:Description rdf:nodeID="A0"> <j.0:oauthConsumerPreAuthId>jts_user</j.0:oauthConsumerPreAuthId> <j.0:oauthConsumerName>Jazz Team Server</j.0:oauthConsumerName> <j.0:oauthConsumerTrusted>true</j.0:oauthConsumerTrusted> <j.0:oauthConsumerSecret>secret</j.0:oauthConsumerSecret> <j.0:oauthConsumerKey>key</j.0:oauthConsumerKey> <rdf:type rdf:resource="http://jazz.net/xmlns/foundation/1.0/OauthConsumer"/> </rdf:Description></rdf:RDF>
How to resolve this issue and successfully register RM on JTS in distributed topology.
|
One answer
![]()
David Honey (1.4k●1●7)
| answered Oct 19 '22, 4:52 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER I recommend that you submit a ticket with IBM technical support. This forum is not a replacement for normal support channels.
|
Comments
Bare hostnames like https://windows-vm2-rm:9443 aren't recommended, this might be the problem?