It's all about the answers!

Ask a question

RTC 4.0.2 - How to fix different OAuth domains errors?


carlos roberto (21443030) | asked Apr 19 '13, 10:48 a.m.
edited May 20 '13, 6:28 p.m. by Millard Ellingsworth (2.5k12431)
1. My first scenario was RTC 3.0.1 using hostname AAA.com
2. Upgraded to 4.0.2 where the hostname now is BBB.com
3. I had to a rename server process from AAA.com to BBB.com
4. After fix some errors, now I am able to start /jts and /jazz but when I open /jts, the diagnostic shows the error below. I am not sure, but looks like I need re-register /jazz and /admin using the new URI but I have seen in some posts that I will lose my data. Looks like I am near my target now. Is there any documentation or post to guide me to fix this issue? I am using Tomcat and I have all the things hosted in a single server.
Thanks.

Application: the discovery resource at https://bbb.com:9443/jazz/rootservices for "/jazz" has different OAuth domains than the entry does.
OAuth domains from the discovery resource: [https://aaa.com:9443/jazz]
Application OAuth domains: [https://bbb.com:9443/jazz]
Application: there is no OAuth domain in the discovery resource at https://bbb.com:9443/jazz/rootservices for "/jazz" that is a prefix of the discovery resource URI.
This could be caused by changing the public URI setting in the application or friend.
OAuth domains from the discovery resource: [https://aaa.com:9443/jazz]
Application: there is no OAuth domain in the discovery resource at https://bbb.com:9443/admin/rootservices for "/admin" that is a prefix of the discovery resource URI.
This could be caused by changing the public URI setting in the application or friend.
OAuth domains from the discovery resource: [https://aaa.com:9443/admin, https://bbb.com:9443/jts]


Comments
Millard Ellingsworth commented May 20 '13, 6:27 p.m.
FORUM ADMINISTRATOR / JAZZ DEVELOPER

Hi, Carlos. Did you resolve your issue yet? 


carlos roberto commented May 21 '13, 8:47 a.m.

Hi Millard

Still not fixed.

Thanks.


Piotr Aniola commented May 21 '13, 8:59 a.m. | edited May 21 '13, 9:00 a.m.


Please note, 3.0.1 is supposed to have a background task that finds and fixes these errors every once in a while.
https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=163425


carlos roberto commented May 21 '13, 9:12 a.m.

I've migrated from 3.0.1 to 4.0.2 so I dont have 3.0.1 running on the new server. It sounds like there was an issue during upgrading / conversion but because it is an OAuth issue I guess it is possible to fix it editing some configuration file or reinstalling some app but I am not sure what to do. I did search some posts but could not find something to guide me.

One answer



permanent link
Stephanie Bagot (2.1k1513) | answered Jun 04 '13, 12:44 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
As mentioned, you should re-register the applications. This will not cause any major issues unless you are using RRC. For RRC - Do not re-register the application. Open up a PMR with IBM Support.

@Piotr it looks like that work item is to correct the RRC entries for QM and CCM, but I don't know if it is running on JTS?

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.