After upgrading CUC to 11.0, the web inbox link on our website no longer works

miketennyson · ‎06-06-2016

On our company internal website, we have the CUC web inbox linked for users to click on when they forget their voicemail password: https://cuc server/inbox/. After upgrading to 11.0, when users click on the link, they get:

HTTP Status 403 -

type: Status report

message:

description: Access to the specified resource has been forbidden.

If they click the URL in the address bar and hit enter, it then takes them to the page to log in. It seems as though the redirect is the problem. Has anyone else run into this issue?

Shashank Mahajan · ‎06-07-2016

The upgrade to Unity Connection version 11.0 should not affect the access to Web inbox link unless there is a change in the host name. If the redirect isn't working then you can check the forward and reverse lookup on your DNS server.

miketennyson · ‎06-08-2016

The host name didn't change. Both forward and reverse lookups are providing the correct name on both the PCs and the server. The URL works if you copy it out and drop it in any browser. The link doesn't work from a redirect from our website however which started immediately after the upgrade. It opens a new tab, throws the 403 error but then works if you put the cursor in the address bar and hit enter again.

Leszek Wojnarski · ‎06-08-2016

hi Mike,

Have you tried: utils service restart Cisco Tomcat, just to make sure nothing is stuck on tomcat?

If you have cluster then is this the same on both Publisher and Subscriber?

Leszek

miketennyson · ‎06-08-2016

I've tried restarting the service multiple times as well as bouncing the servers. I do have a cluster and I have the same issue on both servers.

Leszek Wojnarski · ‎06-09-2016

Hi Mike,

Thanks for information. Can you try to reproduce the issue, and then collect Audit, Tomcat and Event Viewer application logs. Once those are collected please attach them to your post.

Please specify time and date of the test and IPs of client and Server.

Additionally couple of questions:

- have you tried different browsers?

- do you have any proxy or firewall between PC and CUC?

Leszek

miketennyson · ‎07-12-2016

Sorry in advance for the dumbed down response, I am not versed in website administration. We use a portal solution for our intranet page that allows user info to be passed along when you link to a website/application which broke in version 11. I am guessing Cisco secured tomcat a little better and because Cisco doesn't apparently allow info to pass to the login page, it throws the 403 error. I asked Cisco if there was anything we could do to allow the user info to pass to the login page and was told no.

We ended up opening a ticket with the portal vendor and their simple solution was to have us use buttons rather than links because the buttons don't pass user info. This was our work around.

BILL BARTLETT · ‎01-04-2017

We have the same problem on Connection 11.5.1. I have tried it with multiple browsers and the behavior is the same. Also, the server name did not change. If I click a SharePoint link, I get the 403 error. If I paste the link, it works. Also, on a page where I got the 403 error, if I click on the address bar, at the end of the address and press enter (not refresh), then it also works. If I have the url in a Word document and click the hypertext link, then it also works. This may be related to SharePoint.

Thomas Quinn · ‎07-12-2016

Hi, did you ever find a solution to this issue? we've just come upon it as well...

Thanks!

miketennyson · ‎07-12-2016

We use a portal solution for our intranet page that allows user info to be passed along when you link to a website/application which broke in version 11. I am guessing Cisco secured tomcat a little better and because Cisco doesn't apparently allow info to pass to the login page, it throws the 403 error. I asked Cisco if there was anything we could do to allow the user info to pass to the login page and was told no. We ended up opening a ticket with the portal vendor and their simple solution was to have us use buttons rather than links because the buttons don't pass user info. This was our work around.

Thomas Quinn · ‎07-12-2016

Thanks for the response, though not ideal, I'm also looking into this with our cisco team. in my case, the link is literally just a link, sending you to the URL, I might have to try a button though, not sure what difference it would make.

Thanks!

Sascha Monteiro · ‎04-05-2017

if it's a link (a), add this element: rel="noreferrer"

we had the same issue and this seems to have helped

rpmangala · ‎06-26-2017

we had this issue with webdialer. we used noreferrer with header. this worked for us!!!!

miketennyson · ‎06-27-2017

I will test this and if it works, you'll get the "Correct Answer" award. Thanks Sascha.

Randy Krudop · ‎08-09-2017

We've just had the same happen after our Unity 11.5.1 upgrade, making some of our knowledge article links to Unity PCA forbidden now. Can you please share the exact characters how to add this element to the end of the URL. For example, what exactly do I add after the "do" in our PCA URL:

https://[hostname]/ciscopca/home.do

Not an HTML guy by any stretch. Also, I'm reaching out to TAC to see if this is a known defect and/or what the "official" fix is. Thanks.