Skip to main content
N
Naveen_K5-Regular Member
5-Regular Member
April 25, 2024
Solved

Thingworx view in browser ask Authentication while publishing project from outside of vuforia studio

  • April 25, 2024
  • 1 reply
  • 849 views

Dear Team,

 

I have published a project outside of vuforia studio using

curl -u <userId>:<password> -F ThingXExperience=@<myabcapp.zip> -H "X-Requested-With: XMLHttpRequest" https://localhost:2019/ExperienceService/content/projects/

and project is published successfully, But if I try to open ThingWorx view from browser using http://xxxxx/ExperienceService/content/projects/project_name/index-desktop.html?

 it ask user name & Password. It was not the case 4 months before.

I also set "accessType": "public", in metadata.json.

 

I tested publishing project within Vuforia studio and tried ThingWorx View URL in browser it works without asking Username & Password.

 

Can you please help me on this, I need to publish project outside of vuforia studio and i need to access ThingWorx view in browser without asking username & password.    Thanks

 

Regards

Naveen

Best answer by RolandRaytchev

Hi @Naveen_K,

you can also use the Studio UI and unpublish the proejct.

2024-04-29_12-56-46.jpg

Later you can publish the proejct. What is the effect then?

 

In generally regarding to this issue - there could be found related informaiton in some  PTC TechSupport articles -> example: https://www.ptc.com/en/support/article/CS284529

saying in resoltuion something like this:

//================

Workaround:
  • an Experience Service could be called in a preview mode  through  URL e.g. ​:
  • workaround works for  Vuforia Studio Version 8.1.x with the default program setting
  • with version 8.2.xx and newer the workaround requires addtional settings in the configuration file :    <Windows OS User>\Documents\VuforiaStudio\builder-settings.json
  • the following options could be set in the builder-setting.json file:
"publishPreview": true  - allow to publish the preview to a browser outside the Studio environment 
       or
"enableDebugLogging": true  - the option enables the Debug logging in  the Studio settings
  • ​​​​​​​user could set the option "enableDebugLogging" also via Vuforia Studio UI ->Settings -> checkbox Enable Debug Logging

Also possibly the following configuration.json option could be tested if they have effect on this behavior:

{
…..
"nossl":true,
"nohttp2":true
}

//================

 

  • alternatively you can check the call :

curl -u <userId>:<password> -H "Accept:application/json"  http://xxxxx/ExperienceService/ExperienceService/content/projects/project_name/access

which should return the value example :
{"ispublic":false}

here the output is for project which is reported by ES as not public

  • in case of that call  you need always for this request /Rest API call on server user/password. So Rest API call without credentials should not work so far I know.
  • you can also check if you project is correctly reported from the ES  in the metadata is ok so you can try:

curl -u <userId>:<password> -H "Accept:application/json"  http://xxxxx/ExperienceService/ExperienceService/content/projects/ >>output_data.txt

and check then in the output the data what is returned - so possibly you can find some setting

  • If the project is not there you can publish it:
    curl -u user:password -H "X-Requested-With: XMLHttpRequest" -F "File=@MyProject.zip" https://localhost:2019/ExperienceService/content/projects/​
  • when is already there you try to override it (but the same could be done by the Studio UI as TEST)
curl -X PUT -u user:password -H "X-Requested-With: XMLHttpRequest" -F "File=@MyProject.zip" https://localhost:2019/ExperienceService/content/projects/myproject
curl -u user:password -H "X-Requested-With: XMLHttpRequest" -F "File=@MyProject.zip" https://localhost:2019/ExperienceService/content/projects?replace=true

 

  • you can try also to delete existing project with some call like this
    curl -u user:password -H "Content-Type: Application/JSON" -H "X-Requested-With: XMLHttpRequest" -X "DELETE" https://localhost:2019/ExperienceService/content/projects/myproject/​

I did use such calls in the past but could not remember to have some issue as described in your topic so possibly you can check if this info is helpful in your case. Thanks

 

 

 

1 reply

R
RolandRaytchev21-Topaz IAnswer
21-Topaz I
April 29, 2024

Hi @Naveen_K,

you can also use the Studio UI and unpublish the proejct.

2024-04-29_12-56-46.jpg

Later you can publish the proejct. What is the effect then?

 

In generally regarding to this issue - there could be found related informaiton in some  PTC TechSupport articles -> example: https://www.ptc.com/en/support/article/CS284529

saying in resoltuion something like this:

//================

Workaround:
  • an Experience Service could be called in a preview mode  through  URL e.g. ​:
  • workaround works for  Vuforia Studio Version 8.1.x with the default program setting
  • with version 8.2.xx and newer the workaround requires addtional settings in the configuration file :    <Windows OS User>\Documents\VuforiaStudio\builder-settings.json
  • the following options could be set in the builder-setting.json file:
"publishPreview": true  - allow to publish the preview to a browser outside the Studio environment 
       or
"enableDebugLogging": true  - the option enables the Debug logging in  the Studio settings
  • ​​​​​​​user could set the option "enableDebugLogging" also via Vuforia Studio UI ->Settings -> checkbox Enable Debug Logging

Also possibly the following configuration.json option could be tested if they have effect on this behavior:

{
…..
"nossl":true,
"nohttp2":true
}

//================

 

  • alternatively you can check the call :

curl -u <userId>:<password> -H "Accept:application/json"  http://xxxxx/ExperienceService/ExperienceService/content/projects/project_name/access

which should return the value example :
{"ispublic":false}

here the output is for project which is reported by ES as not public

  • in case of that call  you need always for this request /Rest API call on server user/password. So Rest API call without credentials should not work so far I know.
  • you can also check if you project is correctly reported from the ES  in the metadata is ok so you can try:

curl -u <userId>:<password> -H "Accept:application/json"  http://xxxxx/ExperienceService/ExperienceService/content/projects/ >>output_data.txt

and check then in the output the data what is returned - so possibly you can find some setting

  • If the project is not there you can publish it:
    curl -u user:password -H "X-Requested-With: XMLHttpRequest" -F "File=@MyProject.zip" https://localhost:2019/ExperienceService/content/projects/​
  • when is already there you try to override it (but the same could be done by the Studio UI as TEST)
curl -X PUT -u user:password -H "X-Requested-With: XMLHttpRequest" -F "File=@MyProject.zip" https://localhost:2019/ExperienceService/content/projects/myproject
curl -u user:password -H "X-Requested-With: XMLHttpRequest" -F "File=@MyProject.zip" https://localhost:2019/ExperienceService/content/projects?replace=true

 

  • you can try also to delete existing project with some call like this
    curl -u user:password -H "Content-Type: Application/JSON" -H "X-Requested-With: XMLHttpRequest" -X "DELETE" https://localhost:2019/ExperienceService/content/projects/myproject/​

I did use such calls in the past but could not remember to have some issue as described in your topic so possibly you can check if this info is helpful in your case. Thanks

 

 

 

Terms & ConditionsCookie settingsAccessibility statement