Personas 3.0 Whitelist Issues

[Former Member]

We recently installed version 3.0 after doing extensive proof-of-concept work in version 2.0 and have run into trouble trying to launch a website.

I have gone in and added the configuration recommended for this fix. The way I did it was I went to /personas/admin transaction --> GoTo --> URL Whitelist, and added the following configuration: HTTP_HTTPS in "Whitelist-Id" and (http|https):W* in "URL-Whitelist-Expression". We are still not able to launch a website from a flavor.

We additionally applied note 2187907 - Date: 2015-07-17 - SAP Screen Personas 3.0 SP01 : Editor shows incorrect url whitelist error message, but still no luck.

Lastly, we did the general personas configuration in the SPRO tree and entered a * in the Maintain Whitelist URL section.

Is there something I have missed that is still keeping us from using this feature?

Thanks!

[tamas_hoznek · Accepted solution]

The whitelist expression to allow all web sites should be (http|https):\/\/* (so backslash - slash - backslash - slash) and not with a W... yes, I realize this can be confusing and it looks like a W at first glance.

The SPRO section for Personas is related to version 2.0 and it has nothing to do with version 3.0

[Former Member · Accepted solution]

Thanks - I have updated the settings but still when I exit my flavor, I still get the warning message: "This flavor contains non-whitelisted URL. Please contact your system admin" even though we have done everything that I believe needs to be done for setup. No luck in launching a webpage so far.

Are there any other things that we need to do first to be able to launch a webpage, or should those steps have taken care of it?

Thanks,

Justin

[tamas_hoznek · Accepted solution]

Did you log out of your Personas session and closed all the browser windows after adjusting the whitelist?

[Former Member · Accepted solution]

Hello Tamas -  I work with Justin Kumar, and we are still having web button issues in Personas 3.0.  We have the whitelist table configured as you requested.  There is no error message of whitelist any longer.  However, when any of the web buttons that were created in personas and once working, are executed, they are no longer working or giving an error message.  The button does not respond, and, therefore no website returned....Any suggestions?  Please advise.

[tamas_hoznek · Accepted solution]

Hi Daniel,

Sorry, I just realized that I made a typo in the whitelist expression above. It is missing a period... so it should be (http|https):\/\/.* - or actually, (http|https):.* is also fine, if you want the whitelist to restrict access to addresses starting with http or https.

Even .* is sufficient if you don't care about the protocol and want to allow anything and everything.

If after this, accessing URLs still doesn't work then verify if your system is fully up-to-date, with all applicable notes according to the master note implemented. The Personas client should also be on its latest version.

Tamas.

[Former Member · Accepted solution]

Awesome!  Thanks for the information!

That worked.  In modifying the original entry, we noticed that we cut and pasted the whitelist expression: (http/https):VV* .  However the "VV" that was originally copied from the forum, apparently was really entered as: "\/\/", which was a backwards slash, forward slash, backward slash, forward slash.  Hence this was really causing the issue.  Once we added the alphabet letter of "V", and the period *, the entry worked fine, and we were able to access the web page via the button created in Personas.

Thanks so much for your help!

[tamas_hoznek · Accepted solution]

Hmm... I'm confused now.

There should be no alphabet letter V or W in that whitelist entry. If anything, then it should indeed be backward slash, forward slash, backward slash, forward slash.

But I'd rather suggest the (http|https):.* entry, so leave the slashes off.

[Former Member]

Hi Justin,

Please see my post: "Personas 3.0 SP02 PL300: HTML Viewer is not shown" (sorry I don't know how to paste the post link) where I have whitelist detailed examples.

Basically, there are two ways to do:

1- General cases, use RegExp to whitelist the url. I think the info in the guide doc are not all work. This way you can validate a set of urls. See my example to valid all Google sites.

2- Or for a specific url only, you just copy/paste the url and escape all the special charactors in the url. (slash, dot etc, see the example in the post too) This is pretty straight forward for a speific url.

Hope this helps.

Dong Zhu