Error accessing Reality Model in ContextShare #2091
-
|
I am trying to move my code to the latest (2.19.6) iTwin (from 2.15.2). I created a new application as my existing application didn't seem to work with 2.19.6 (not sure if this statement is correct but I was having problems so I created a new application). I am getting http error when I try to query reality data info from ContextShare. I have realitydata:modify and realitydata:read specified in my scope and also enabled in application. I recall that last time that Bentley had to do something manually (add realitydata scopes) to the application to get it to work (wondering if this is same issue).
The following queryRealityData() call is failing ======= ======= Request URL: https://api.bentley.com/contextshare/v1/Repositories/S3MXECPlugin--d20678d8-ad8c-4732-a32f-5ec62e2befc0/S3MX/RealityData?project=d20678d8-ad8c-4732-a32f-5ec62e2befc0&$filter=Type+eq+%27RealityMesh3DTiles%27+or+Type+eq+%27OPC%27+or+Type+eq+%27Terrain3DTiles%27+or+Type+eq+%27OMR%27+or+Type+eq+%27Cesium3DTiles%27 ======= HEADER:ALGORITHM & TOKEN TYPE { PAYLOAD:DATA bf": 1629297635, |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 13 replies
-
|
The one thing that I think is missing is that you are not using the new IMS Authority url when getting your token. You can look here for an example of how to configure it, #1699 (reply in thread). I was also told that a blog post to help users migrate should be published soon... |
Beta Was this translation helpful? Give feedback.
-
|
Hi Eric, I was not trying to migrate authentication of my existing app (as per #1699) , instead I created a new iTwin app for this so I expect it should be (and seems to be - pls see decoded token below) using the new authentication based on IMS authority. Note the "aud" and "iss" fields, both seem to point to IMS. Reality data related scopes are included and are set in the client app too. For demonstration of the issue, I created a new app from iTwin react template today and added code to query for reality data. Please see attached xviewer.zip at bottom of this post. My changes are: I added 'onIModelConnected' parameter to the 'Viewer' and added its callback (all changes in App.tsx). The callback code is: const onIModelReady = async (imodel: IModelConnection) => { Note that I am using the Bayview Plant model with this app. The project doesn't have any reality data associated with it, but the call should not fail (and doesn't fail in my old project). It should zero reality data models, rather than 401 error. If for debugging purposes, anyone needs access to my test project, I'll be happy to add them in, please let me know. === Error ====
==== Decoded token ===== ==== client scopes ====
==== XVIEWER.ZIP ==== |
Beta Was this translation helpful? Give feedback.
-
|
Ovais, we'll need to investigate this issue further. One possibility is that the realitydata scope is not correctly delegated... Will get back to you. -Eric |
Beta Was this translation helpful? Give feedback.
-
|
Hi Eric, Can I request an update on this. Reality Models are central to our workflow and because of this issue, our progress is stranded. Thank you |
Beta Was this translation helpful? Give feedback.
-
|
Ovais,
Sorry about the long wait. I contacted another team to investigate this issue, because I did not find anything on my side… I’ll push to get feedback.
Thanks,
Eric
From: ovaisa ***@***.***>
Sent: Tuesday, August 24, 2021 1:53 PM
To: imodeljs/imodeljs ***@***.***>
Cc: Eric Paquet ***@***.***>; Comment ***@***.***>
Subject: Re: [imodeljs/imodeljs] Error accessing Reality Model in ContextShare (#2091)
WARNING: This email originated from outside of the organization. DO NOT click links, open attachments, or respond unless you recognize the sender and know the content is safe.
…________________________________
Hi Eric,
Can I request an update on this. Reality Models are central to our workflow and because of this issue, our progress is stranded.
Thank you
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/imodeljs/imodeljs/discussions/2091*discussioncomment-1228877__;Iw!!F1Q1IbZmrAg!TmMz6fLMwOVHhn62xAq-sqwameqf3mvBh97aduC-84Wz189XOlrKTcL8I_-yehBMg8g$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/ATYP2HVZE4L6N4L3LIFPBJLT6PL6XANCNFSM5CMK7X6Q__;!!F1Q1IbZmrAg!TmMz6fLMwOVHhn62xAq-sqwameqf3mvBh97aduC-84Wz189XOlrKTcL8I_-yu7CyVKQ$>.
Triage notifications on the go with GitHub Mobile for iOS<https://urldefense.com/v3/__https:/apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675__;!!F1Q1IbZmrAg!TmMz6fLMwOVHhn62xAq-sqwameqf3mvBh97aduC-84Wz189XOlrKTcL8I_-ySqBxLa4$> or Android<https://urldefense.com/v3/__https:/play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email__;!!F1Q1IbZmrAg!TmMz6fLMwOVHhn62xAq-sqwameqf3mvBh97aduC-84Wz189XOlrKTcL8I_-yziQil-E$>.
________________________________
This email, including any attachments, may contain confidential and/or proprietary information intended only for the use of the recipient. If you are not the intended recipient, any distribution, copying, or use of this email or its attachments is prohibited. If you received this email in error, please reply to the sender immediately and delete this message and any copies.
Bentley Systems has taken all reasonable steps to ensure that this communication is free from viruses, data corruption, and unauthorized alteration. Bentley Systems does not accept liability for any damages that may be incurred as a result of this or any communication by email
[https://cdn2.webdamdb.com/310th_sm_UnR3pO7k0ir0.jpg?1616176329]
|
Beta Was this translation helpful? Give feedback.
-
|
Ovais, Regards, |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the update. Yes, if you can find a workaround, it would be really appreciated. I had similar problem with accessing reality data a while back and Bentley added some scope privileges (or something) manually behind the scenes in the clientapp which at least helped me continue with my development work. If there is such a work around, it will be very helpful. Thanks, Ovais |
Beta Was this translation helpful? Give feedback.
-
|
Sure, I remember. The issue is still related to scopes, but the situation is a bit different this time. In any case, we’re actively working on pushing a fix.
Eric
From: ovaisa ***@***.***>
Sent: Wednesday, August 25, 2021 9:31 AM
To: imodeljs/imodeljs ***@***.***>
Cc: Eric Paquet ***@***.***>; Comment ***@***.***>
Subject: Re: [imodeljs/imodeljs] Error accessing Reality Model in ContextShare (#2091)
WARNING: This email originated from outside of the organization. DO NOT click links, open attachments, or respond unless you recognize the sender and know the content is safe.
…________________________________
Thanks for the update. Yes, if you can find a workaround, it would be really appreciated.
I had similar problem with accessing reality data a while back and Bentley added some scope privileges (or something) manually behind the scenes in the clientapp which at least helped me continue with my development work. If there is such a work around, it will be very helpful.
Thanks, Ovais
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/imodeljs/imodeljs/discussions/2091*discussioncomment-1233247__;Iw!!F1Q1IbZmrAg!UMzPJ0EMPmmIUVfozze6yyiyQXKHj528qZLnR_H4nlClt9lvw_vBQkMwQd93wJB2yFE$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/ATYP2HT7RD6SFCIDN2EEBLDT6TWBHANCNFSM5CMK7X6Q__;!!F1Q1IbZmrAg!UMzPJ0EMPmmIUVfozze6yyiyQXKHj528qZLnR_H4nlClt9lvw_vBQkMwQd93OMhBA0M$>.
Triage notifications on the go with GitHub Mobile for iOS<https://urldefense.com/v3/__https:/apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675__;!!F1Q1IbZmrAg!UMzPJ0EMPmmIUVfozze6yyiyQXKHj528qZLnR_H4nlClt9lvw_vBQkMwQd93UL1cclE$> or Android<https://urldefense.com/v3/__https:/play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email__;!!F1Q1IbZmrAg!UMzPJ0EMPmmIUVfozze6yyiyQXKHj528qZLnR_H4nlClt9lvw_vBQkMwQd9323Ukaik$>.
________________________________
This email, including any attachments, may contain confidential and/or proprietary information intended only for the use of the recipient. If you are not the intended recipient, any distribution, copying, or use of this email or its attachments is prohibited. If you received this email in error, please reply to the sender immediately and delete this message and any copies.
Bentley Systems has taken all reasonable steps to ensure that this communication is free from viruses, data corruption, and unauthorized alteration. Bentley Systems does not accept liability for any damages that may be incurred as a result of this or any communication by email
[https://cdn2.webdamdb.com/310th_sm_UnR3pO7k0ir0.jpg?1616176329]
|
Beta Was this translation helpful? Give feedback.
-
|
Ovais, we have a fix for your issue. We'll push it in the coming days. There does not seem to be a workaround in the meantime, unfortunately. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you Eric for following up, glad to hear that fix will be available in the next push. If it is possible to share the timeline of that push, it will help me manage our user expectation. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Eric, I wanted to point out from last time we ran into this issue. If you recall, the access to reality model access was working in development mode (localhost:3000) but it was not working when I deployed the site on Netlify. I recall that Glen commented that the access worked within Bentley domain/network but it was an issue when accessing from outside Bentley domain (that is why it was not caught in testing by Bentley). Not sure if that was really the issue, I hope that this is checked before pushing the new version (as it would cause more delays on our side if their were similar problems accessing from outside Bentley domain) Thanks, Ovais |
Beta Was this translation helpful? Give feedback.
-
|
Hi Ovais, Thanks, |
Beta Was this translation helpful? Give feedback.
-
|
I am afraid I am still getting the same error
Request URL: https://api.bentley.com/contextshare/v1/Repositories/S3MXECPlugin--d20678d8-ad8c-4732-a32f-5ec62e2befc0/S3MX/RealityData?project=d20678d8-ad8c-4732-a32f-5ec62e2befc0&$filter=Type+eq+%27RealityMesh3DTiles%27+or+Type+eq+%27OPC%27+or+Type+eq+%27Terrain3DTiles%27+or+Type+eq+%27OMR%27+or+Type+eq+%27Cesium3DTiles%27 origin: http://localhost:3000 **** DECODED TOKEN **** |
Beta Was this translation helpful? Give feedback.
-
|
Created a new client, same error Request URL: https://api.bentley.com/contextshare/v1/Repositories/S3MXECPlugin--d20678d8-ad8c-4732-a32f-5ec62e2befc0/S3MX/RealityData?project=d20678d8-ad8c-4732-a32f-5ec62e2befc0&$filter=Type+eq+%27RealityMesh3DTiles%27+or+Type+eq+%27OPC%27+or+Type+eq+%27Terrain3DTiles%27+or+Type+eq+%27OMR%27+or+Type+eq+%27Cesium3DTiles%27 { |
Beta Was this translation helpful? Give feedback.
-
|
Ovais, -Eric |
Beta Was this translation helpful? Give feedback.
-
|
Ovais, the release of the fix is complete. Please retry to run your app and let me know how it works. -Eric |
Beta Was this translation helpful? Give feedback.
-
|
Thank you Eric, yes it is working!!! Much appreciate your diligence and follow up to get this resolved... |
Beta Was this translation helpful? Give feedback.
-
|
Great ! Very glad to hear it ! Sorry for the trouble, hope it goes more smoothly in the future. -Eric |
Beta Was this translation helpful? Give feedback.
The one thing that I think is missing is that you are not using the new IMS Authority url when getting your token.
You can look here for an example of how to configure it, #1699 (reply in thread).
I was also told that a blog post to help users migrate should be published soon...