It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×5,996
×3,952

question asked: Jan 23 '13, 2:51 p.m.
question was seen: 4,177 times
last updated: Jan 30 '13, 3:53 p.m.

Related questions

FAQ - How this Forum works

No longer able to log in to RM

0
Erich Wolz (162●2●7●11) | asked Jan 23 '13, 2:51 p.m.
edited Jan 23 '13, 2:53 p.m.
A few months ago I set up an RRC 4.0.0.1 instance for a user.  It was all set up but then funding stalled.  Funding has become available again, but now we're unable to login to the /rm/web application. 

The only thing that I know has changed is, the WAS server was upgraded to 7.0.0.25, from whatever it was at the time the instance was set up.  After the upgrade, I was able to log in to the /jts/admin; the status summary and diagnostics looked ok (i.e. everything green), but that's all I checked at the time of the upgrade (since I knew the server was not actively in use).

Here's the message we are currently getting:

ID CRRRW7558E  The server indicates that it does not permit the operation. The message that follows might include additional information about why the operation is not permitted.
Unable to load /rm/proxy?uri=https%3A%2F%2Flocalhost%3A9444%2Frdm%2Fstoredquery&dojo.preventCache=1358970790929 status:403
([object Object])@https://houaxpcm01.houston.ibm.com:9443/rm/web/_js/?include=A~&etag=BNReZ4yO63G_en_US&_proxyURL=%2Frm&ss=BirvM:15 ()@https://houaxpcm01.houston.ibm.com:9443/rm/web/_js/?include=A~&etag=BNReZ4yO63G_en_US&_proxyURL=%2Frm&ss=BirvM:15 (-14)@https://houaxpcm01.houston.ibm.com:9443/rm/web/_js/?include=A~&etag=BNReZ4yO63G_en_US&_proxyURL=%2Frm&ss=BirvM:15

URL: /rm/proxy?uri=https%3A%2F%2Flocalhost%3A9444%2Frdm%2Fstoredquery

Error 403: The proxy is not configured to allow the request to https://localhost:9444/rdm/storedquery. There may be a missing friend entry for this server.


I searched the forum and found https://jazz.net/forum/questions/82419/missing-friend -- which states that the "missing friend" is in QM.  So I checked /qm/admin#action=com.ibm.team.repository.admin.friends but found JTS, CCM, and RM already listed as friends.  The OAuth Consumer Key for RM matches what's in the server's conf/rm/friendsconfig.rdf file.

Any other ideas/suggestions for things to check?

Accepted answer

1
permanent link
Bas Bekker (1.4k●4) | answered Jan 23 '13, 4:37 p.m.
JAZZ DEVELOPER
edited Jan 23 '13, 4:39 p.m.
Are your RM licenses still good, i.e. not expired?
Check in the JTS admin pages, /jts/admin -> server menu -> license key management
Erich Wolz selected this answer as the correct answer
Comments
Erich Wolz commented Jan 23 '13, 6:53 p.m.

License Key Management shows that I have the following active CAL types (not counting the "Internal" and/or "Included" ones):

RQM Quality Professional-Floating: Unlocked, Active (0 assigned)
RRC Analyst-Floating: UInlocked, Active (11 assigned)
RTC Developer for IBM Enterprise Platforms-Floating: Unlocked, Active (1 assigned)

The "Floating License Server" portion of the screen, further down, shows a total of 3 RQM Quality Professional-Floating licenses, 3 RRC Analyst-Floating licenses, and 10 RTC Developer for IBM Enterprise Platforms-Floating licenses.

Bas Bekker commented Jan 23 '13, 7:08 p.m.
JAZZ DEVELOPER

Hi Erich,
Can you check if the /server/conf/rm/fronting.properties file still has entries with https://localhost:9444/rdm ?
That value made me suspicions as it is the initial value set in that file before the JTS setup wizard runs, and registers and finalizes the RM app.

Erich Wolz commented Jan 29 '13, 7:05 p.m.

Sure enough, a grep for 9444 on the fronting.properties file turns up the following:

com.ibm.rdm.fronting.server.dnghelp=https\://localhost\:9444/rdm
com.ibm.rdm.fronting.server.RDMWebAppFoundationProjectDashboardUrl=https\://localhost\:9444/rdm/web#action\=com.ibm.rdm.web.pages.showFoundationProjectDashboard&projectURI\=
com.ibm.rdm.fronting.server.RDMFrontsideURL=https\://localhost\:9444/rdm
com.ibm.rdm.fronting.server.RDMWebAppDataModuleBindingRedirectUrl=https\://localhost\:9444/rdm/web#action\=com.ibm.rdm.web.pages.showArtifact&artifactURI\={moduleURI}&artifactInModule\=

I thought that maybe rerunning setup would clear things up, but setup hung up on the "Finalize RM" step, with "Firefox can't establish a connection to the server at localhost:9444"

Do I want to change the 9444's to 9443's?  or do I want to change the localhosts to the FQDN?  or something else?

1
Erich Wolz commented Jan 30 '13, 3:53 p.m.

Documenting the results of a follow-up chat with Bas:

Running https://houaxpcm01.houston.ibm.com:9443/rm/rootservices directly in my browser established that RM is definitely listening on port 9443, so I changed all 9444's to 9443 and restarted WAS - but that was not enough.

friendsconfig.rdf had the following:
<jfs:oauthDomain>https://localhost:9443/jts</jfs:oauthDomain>
I replaced "localhost" with a FQDN and restarted WAS - but that was still not enough.

I re-checked /rm/rootservices, and the value for <rm:setupWizardDescriptor rdf:resource="  ">  was:
https://houaxpcm01.houston.ibm.com:9443/rdm/setupWizardDescriptor

Not sure why (or how) the URL context was /rdm and not /rm, but there were 12 other occurrences of /rdm in fronting.properties. I can't even imagine a scenario where I would have changed these, not once, but 13 times! I changed all /rdm to /rm and restarted WAS.

Now, pointing my browser directly to the setupWizardDescriptor URL returned the expected response; /jts/setup made it past the "Finalize RM" step; and I am again able to login to /rm/web

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.