Not getting the Delegated UI dialogs in the RDNG.
Hi All,
I have implemented one RDNG provider using 'bugzilla oslc adapter' as a reference. It has one Service Provider (RM_Service_Provider) for Requirements Management. The provider is able to provide the delegated UI for both selection and creation. I have tested the UI in the browser as well, it is working fine in the browser. So I expected that when i go to RDNG and brows any requirement and when i add any link like 'implemented by' or 'tracked by' , the delegated UI from my provider should open up. i have done all the prerequisite like server friending, project association. Problem : The problem i am facing now is when i try to add any link and clicks on any of 'select existing' or 'create new', i am not getting the selection or creation dialog. it is showing blank. Also i tried to check the log for any error, but no log is generated. |
Be the first one to answer this question!
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.
Comments
Have you monitored the HTTP traffic to see if the browser or RDNG tries to get the dialog? SSO or cross-site references may be at play here but without some debugging it is hard to say.
Hey Donald,
yes it tries to get the dialog, when i select the provider it first asks me the credentials through a popup which is provided by my provider, to login into my RDNG provider. but after giving the credentials, i am getting the blank response.
i believe, if any of problem is there as you mentioned then, it should not ask for the credentials also.
so, if you suggest any idea what to debug, where to look exactly..? would be helpful.
In this case, I can think of two scenarios where you will get a "blank page". First is that the login is successful and the server responds with an HTTP 302 and "Location" header for redirecting. You application should then request the URL specified in the "Location" header. The second is something goes wrong after the login and the server returns HTTP 4xx or 5xx code, and you need to debug further depending on the exact code you receive.