Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Unable to get images from DNG due to auth credential issues

Hi,

Unfortunately i'm not able to get the images from DNG due to auth credential issues. I get the below error...

Configuration-Context:
Error in engine
Can not redirect to the OAuthentication identify URL.
Reponse message: OK: <!DOCTYPE html>

and it more...

I have used the 'inherit configuration' feature in the data configuration element to configure the DOORS Next Text schema from the DOORS Next Module schema.

Is there anything i'm missing?

Note I can get diagrams from Rhapsody easily.

Regards,
Srin

0 votes

Comments

"I have used the 'inherit configuration' feature in the data configuration element to configure the DOORS Next Text schema from the DOORS Next Module schema." - please can you explain in more detail what you mean by this, e.g. what did you do to achieve this? 



One answer

Permanent link

 What is the URI provided to configure the data source? From the response, it seems DNG reportable REST URL is not used.

0 votes

Comments

For the DOORS Next Module schema I use the below URI as an example...


For the DOORS Next Text schema I use the below URI as an example...

What schema should I using instead? Thanks.

 Please make sure you are using text schema (and not resources schema). dataSource/artifact/content/text/richTextBody/div from text schema will print the image from the text artifact.

I still get the credentials issue. Any other ideas? 

Because the Reportable REST API doesn't need any specific headers you can use the URL in a logged-in browser tab - start by getting e.g. https://SERVER:PORT/rm/publish/resources/* to work in a browser tab, then use that same (working) URL from your code and see if it works. If there's a credentials error then the problem isn't the API or the URL but something about your code probably related to authentication. Once you don't get an auth error from your code using /publish/resources/* then you can move to trying your real URL - once again, get it working in a browser tab then move it to code.

Your answer

Register or log in 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 12,132

Question asked: Jul 27 '22, 8:08 a.m.

Question was seen: 2,090 times

Last updated: Jul 29 '22, 5:21 a.m.

Confirmation Cancel Confirm