You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cesium for Unreal seems to (sometimes) use the wrong access token for the assets created through the Cesium ion UI.
I saw this while investigating https://community.cesium.com/t/vricon-3dtilesets-are-not-appearing-in-ue4-scene-editor/15277. I started out logged in to my personal ion account, which doesn't have access to the tilesets mentioned. So I clicked the Sign Out button, then "Connect to Cesium ion", then in the web browser I switched to a different ion account that did have access, hit Authorize, and switched back to Unreal. So far so good.
Then I navigated to a Vricon dataset in the Cesium ion Assets panel and added it and got a 404 error. Weird. I copied down the key that the UI had assigned to the Tileset, and then in the ion web UI I confirmed that this was not the right key for the new account. In fact, it was the key for my personal account that I had just signed out of.
So I signed out again, signed back in, re-added the dataset... and this time it worked fine. In fact, I haven't been able to reproduce the problem since.
Which reminded me that I saw a similar problem awhile ago. In that case, I was adding a new Imagery dataset as a raster overlay, and the UI didn't assign it a token at all (it was just blank). That time, too, just trying again fixed it.
So I'm not sure exactly what's going on here, but it's pretty clear that something is wrong with the token management.
The text was updated successfully, but these errors were encountered:
For what it's worth, I'm actually not able to view Vricon datasets in Cesium for Unreal either. Tested with a few different cities, and I'm positive they're using the right token, because I created a token specifically for access to a Vricon dataset and copied it straight in. Always results in errors like:
LogCesium: Error: [2021-09-16 16:48:28.794] [error] [Tileset.cpp:158] Received status code 401 for asset response https://api.cesium.com/v1/assets/97228/endpoint
LogCesium: Loading tileset for asset ID 97228
LogCesium: Loading tileset for asset ID 97228 done
LogCesium: Error: [2021-09-16 16:48:33.080] [error] [Tileset.cpp:158] Received status code 404 for asset response https://api.cesium.com/v1/assets/97228/endpoint?access_token=[token]
@mramato pointed out on Slack that these Vricon datasets are forbidden from use outside of Cesium ion / Cesium Stories, and that ion enforces that. I believe the key mixup issue described here is still a thing, though.
Cesium for Unreal seems to (sometimes) use the wrong access token for the assets created through the Cesium ion UI.
I saw this while investigating https://community.cesium.com/t/vricon-3dtilesets-are-not-appearing-in-ue4-scene-editor/15277. I started out logged in to my personal ion account, which doesn't have access to the tilesets mentioned. So I clicked the Sign Out button, then "Connect to Cesium ion", then in the web browser I switched to a different ion account that did have access, hit Authorize, and switched back to Unreal. So far so good.
Then I navigated to a Vricon dataset in the Cesium ion Assets panel and added it and got a 404 error. Weird. I copied down the key that the UI had assigned to the Tileset, and then in the ion web UI I confirmed that this was not the right key for the new account. In fact, it was the key for my personal account that I had just signed out of.
So I signed out again, signed back in, re-added the dataset... and this time it worked fine. In fact, I haven't been able to reproduce the problem since.
Which reminded me that I saw a similar problem awhile ago. In that case, I was adding a new Imagery dataset as a raster overlay, and the UI didn't assign it a token at all (it was just blank). That time, too, just trying again fixed it.
So I'm not sure exactly what's going on here, but it's pretty clear that something is wrong with the token management.
The text was updated successfully, but these errors were encountered: