Page 1 of 1

Protected website feature

PostPosted: Wed Mar 30, 2016 9:37 am
by ulriklpedersen
Hi

I have noticed a new function in the Build tab called "Protected Website" "(The tour will be hosted on a website protected by credentials)".


What does this function add to the tour?

When do I use it - the documentation does not seem to have been updated with this feature.

We have a lot of tours running in an intranet environment and are currently planning on shifting to IIS and use the build in Windows Credentials login functions - but what does this have to do with Panotour?

Re: Protected website feature

PostPosted: Wed Feb 14, 2018 12:24 am
by edgar_ali
I'm going to upload the tour to a website that will have restrcited access for members. the websites is designed using wordpress and the woocommerce plugin for memberships...

Do i need to use this feature? (Protected website)???

Re: Protected website feature

PostPosted: Wed Feb 14, 2018 12:36 am
by Destiny
If you are referring to the Protection Encryption option during build in PTP, that only edits the XML code so it cannot be viewed as XML readable code. If you have not made any custom features/plugins etc, there is no need to do it.. You can also use the KRPANO encrypt options for this too.. But make sure you make a copy of your XML first.

Destiny..

Re: Protected website feature

PostPosted: Wed Feb 14, 2018 1:02 am
by edgar_ali
Yes I'm referring to the Build tab..however there are two different options in this tab. One is to encrypt the XML files and the other is: Protected website....

What is the protected website option for then?

Re: Protected website feature

PostPosted: Wed Feb 14, 2018 4:50 pm
by bdd
This option is just to ensure the correct load of all the tiles and assets of the tour if this tour is hosted on a website that is protected by credentials/a login.

Leave this option unchecked if the final hosting website does not need a login.

GĂ©rald

Re: Protected website feature

PostPosted: Wed Feb 14, 2018 4:56 pm
by 360-compunics-com-ni
This feature is not related to the encryption of the generated XML-files, it adds a security-related setting that is required when your tours are hosted with individual password protection like HTTP Basic Authentication for example.

Depending on the ressources that are accessed through your tour the setting might not be required (Google for "CORS" for more details). While some browsers ignore the absence of this setting if not strictly required, i noticed that IE refuses to display a tour when HTTP Basic Authentication is used and this setting is not activated. So it's better to activate that option when your tours are not meant to be displayed in public.

Re: Protected website feature

PostPosted: Mon Feb 19, 2018 10:18 am
by edgar_ali
Guys Thanks for your replies...

so just to confirm...If i'm placing my tour behind a paywall, which means that to watch the tour you need to pay for a membership, otherwise you cannot see, then I have to tick "the tour will be hosted on a website protected by credentials"

If i tick this feature and my tour is not hosted in that website protected by credentials, would that be a problem?