It's all about the answers!

Ask a question

Why does a new installation of RDNG 5.0.2 fail with jAuthEndPoint error?

Alejandro Reyes (1438) | asked May 22 '15, 3:38 p.m.
 I am performing a new install (using the interactive install guide) of RDNG 5.0.2 with Tomcat application server, Apache Directory Service, Oracle DB and Windows OS.  During the final steps of the web installation, "Loading" appears but never finalizes.  I receive the following errors in the rm.log file (I've omitted parts and noted where):

<unauthenticated> <Initial Page Load@<omitted>> /jts/auth/authrequired] ERROR            - Unable to retrieve the JAuth service type '' from the configured Jazz Team Server
2015-05-22 10:51:26,038 [<omitted>@@ 14:01 <unauthenticated> <Initial Page Load@<omitted> /jts/customSetup] ERROR            - Unable to retrieve the JAuth service type '' from the configured Jazz Team Server

Why is this error appearing?  Did I configure the JTS, or anything else, incorrectly?  Thanks in advance

Bas Bekker commented May 25 '15, 11:03 a.m.

Where exactly are you in the setup steps when you get stuck in "Loading"?

Can you logon into the JTS server, for example /jts/admin?

One answer

permanent link
Don Yang (7.7k21114139) | answered May 25 '15, 8:19 p.m.
The error "Unable to retrieve the JAuth service type '' from the configured Jazz Team Server " suggests that the discovery service on the JTS is not responding correctly to a query for
JAuth services.
You can verify this by trying the URL:
A correctly configured server will reply with an RDF document with a
jfs:JAuth child.  For example, in my local test, I can see the below result:
<jfs:jauthSigninUrl rdf:resource="https://localhost:9443/jts/jauth-signin"/>
<jfs:jauthCheckAuthUrl rdf:resource="https://localhost:9443/jts/jauth-check-auth"/>
<jfs:jauthProxyUrl rdf:resource="https://localhost:9443/jts/jauth-proxy"/>
<jfs:jauthSSORealmMembers rdf:resource="https://localhost:9443/jts/jauth-sso-realm-members/>
<jfs:jauthCheckTokenUrl rdf:resource="https://localhost:9443/jts/jauth-check-token"/>
<jfs:jauthIssueTokenUrl rdf:resource="https://localhost:9443/jts/jauth-issue-token"/>
<jfs:jauthRevokeTokenUrl rdf:resource="https://localhost:9443/jts/jauth-revoke-token"/>

 If this test does not return the expected output, it suggests that the JTS is somehow misconfigured.  One possible cause of the error is the database - the discovery service queries for these resources are in the jts database.

If you can check with jts.log file, it may provide more clues. If this is a new install, try to reinstall by:
1) uninstall and delete existing instance of CCM and DNG(remove the installed directory after uninstall)
2) drop the DBs
3) re-install CCM and RDNG and create DBs.
4) try to set up again

If the same is seen, I would suggest to engage client support to collect more logs to further investigate. It could be something more complex and need more data to find out the true cause.

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.