It's all about the answers!

Ask a question

Unable to load web UI


Paul Verrone (1361127) | asked Dec 31 '09, 2:10 p.m.
I have a fresh install of RRC 2.0. When I attempt to browse to: https://rrcserver:9443/rdm/web/rrc, it sits on the loading screen.

The following entry shows up in the rdm.log on the server:
http-9443-Processor24] [] ERROR net.jazz.ajax.service.internal.http.ProxyHandler - HttpException while processing OAuth information: CRJZS0033E Invalid consumer key. The consumer may not be registered.

It seems to have started after I tried to set up C/ALM between my RQM and RRC servers. Couldn't get it to work, so I removed all the friend and keys, and restarted and now this.

Any ideas on how I might fix this?

5 answers



permanent link
Robin Bater (3.4k47) | answered Dec 31 '09, 2:43 p.m.
JAZZ DEVELOPER
I have a fresh install of RRC 2.0. When I attempt to browse to: https://rrcserver:9443/rdm/web/rrc, it sits on the loading screen.

The following entry shows up in the rdm.log on the server:
http-9443-Processor24] [] ERROR net.jazz.ajax.service.internal.http.ProxyHandler - HttpException while processing OAuth information: CRJZS0033E Invalid consumer key. The consumer may not be registered.

It seems to have started after I tried to set up C/ALM between my RQM and RRC servers. Couldn't get it to work, so I removed all the friend and keys, and restarted and now this.

Any ideas on how I might fix this?


This maybe a browser cache problem where the previous authentication is still being held onto - so I suggest clearing either your Firefox 3.0+ browser or Internet Explorer 7.0+ browser cache and authentication sessions.

If this is not the problem it might be that you have lost the OAuth Consumer Key for the created RRC tables and the data stored in them when the RRC setup was run - you might need to recreate them by running the setup again.

permanent link
Anuradha Ramamoorthy (16) | answered Jan 04 '10, 3:42 p.m.
JAZZ DEVELOPER
I see the same problem in the RDM log
2010-01-04 15:29:18,484 ERROR ronting.server.services.configure.ConfigureService - CRJZS0033E Invalid consumer key. The consumer may not be registered.
com.ibm.team.jfs.app.oauth.OAuthInvalidConsumerKeyException: CRJZS0033E Invalid consumer key. The consumer may not be registered.

This prevents me from even logging into to https://localhost:9443/rdm/setup
I cleared the cache.
The only difference is I imported an existing repo into my RRC server.
Is it possible that the auth key of the previous repo is not working in the new imported repo?
thanks
Anu

permanent link
Robin Bater (3.4k47) | answered Jan 04 '10, 5:17 p.m.
JAZZ DEVELOPER
I see the same problem in the RDM log
2010-01-04 15:29:18,484 ERROR ronting.server.services.configure.ConfigureService - CRJZS0033E Invalid consumer key. The consumer may not be registered.
com.ibm.team.jfs.app.oauth.OAuthInvalidConsumerKeyException: CRJZS0033E Invalid consumer key. The consumer may not be registered.

This prevents me from even logging into to https://localhost:9443/rdm/setup
I cleared the cache.
The only difference is I imported an existing repo into my RRC server.
Is it possible that the auth key of the previous repo is not working in the new imported repo?
thanks
Anu


Was this a previous repository a RRC V2 repository? If so, yes you will need to use the same oauth consumer key used when that repository was first created.

There might be a way to migrate it (if you have old install) by rebuilding the indexes, these are some instructions I use when I give my repository to others in IBM (but depends upon them having a derby database, tomcat, the same host name and users; the friendsconfig holds the Oauth consumer key) - SO THIS MIGHT NOT WORK FOR YOU, IS NOT OFFICIALLY SUPPORTED, USE AT YOUR OWN RISK and IS NOT RECOMMENDED

1. Install/configure/setup the server keeping the server name set to localhost as opposed to an IP address or machine name
2. Shut down the server
3. Delete repositoryDB folder in <install>\Server
4. Unzip old repositoryDB.zip to <install>\Server
5. Copy old tomcat-users.xml to <install>\server\tomcat\conf
6. Copy old friendsconfig.rdf to <install>\server\conf\rdm
7. Delete the contents of these four folders -

. <install>\server\jfs-rdfhistory ,
. <install>\server\jfs-rdfindex,
. <install>\server\jfs-texthistory,
. <install>\server\jfs-textindex

8. Restart the server
9. Rebuild the configuration https://localhost:9443/rdm/install - press the Install button
10. In browser go to https://localhost:9443/rdm/configure - Click on Rebuild button - login with Username/ Password
11. Let server reindex data for some time.
12. Connect to server using client

Alternatively, do you have the previous repo projects saved as RRC archives? If so, you could upload these archive files into your new installation. This is the method I use to port my data between different V2 builds.

If you old repo is a V1 repo, then during V2 setup you can migrate the data.

permanent link
Nicole Jones (611) | answered Oct 26 '10, 1:10 a.m.
Just installed RRC 2.0. I trying to browse: https://rrcserver:9443/rdm/web/rrc, but it freezes

This is in rdm.log on the server:
http-9443-Processor24] [] ERROR net.jazz.ajax.service.internal.http.ProxyHandler - HttpException while processing OAuth information: CRJZS0033E Invalid consumer key. The consumer may not be registered.


What to do? :?:

permanent link
Robin Bater (3.4k47) | answered Oct 26 '10, 12:16 p.m.
JAZZ DEVELOPER
Just installed RRC 2.0. I trying to browse: https://rrcserver:9443/rdm/web/rrc, but it freezes

This is in rdm.log on the server:
http-9443-Processor24] [] ERROR net.jazz.ajax.service.internal.http.ProxyHandler - HttpException while processing OAuth information: CRJZS0033E Invalid consumer key. The consumer may not be registered.


What to do? :?:


If this a completely new installation or an upgrade from a previous version of RRC?

If it is an upgrade there are some additional upgrade instructions to follow:

https://jazz.net/downloads/rational-requirements-composer/releases/2.0.0.3?p=upgrading

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.