OAAD Picture upload - HTTP Error: 403 Forbidden

[Former Member]

Dear forum,

When trying to upload a picture for our Q/A HR system in tx OAAD I get the error HTTP Error: 403 Forbidden. However, I can do it with no issues in our prod environment. Anyone has an idea why this is? I have checked SICF and icman is enabled. Does anyone have an suggestion? Hence it isnt portal communication I cant use httpwatch, which most likely could have told me whats wrong.

I hope someone is able to comment on this issue.

Thanks in advance!

Kind Regards,

Soren

[Former Member · Accepted solution]

Dear Friis,

We have a steps of configurations that needs to be completed for the photo upload to be working. As you say the same is working in the production system, I hope you have the steps with you.

Most common things that needs to be checked in this scenario are,

1. HTTP service availability through the configured profile parameter in the system

2. Restart after the profile parameter change

3. Content Server node activation in SICF transaction

4. User ID and Password to be mentioned in the SICF service as communications or system user

5. Other checks for the content repository and the number range

You can also try repeatedly, to upload the pic (in a JPG format) - because most usually the first trial ends in a failure for the HTTP service with a 403 Forbidden error message.

Let me know your response and the steps you had followed for the config.

Thank you

Regards,

Vineeth

[Former Member · Accepted solution]

Hi Vineeth,

thank you for your answer. I checked the content server in SICF just to be sure, and I found a difference towards the prod environment (which works)..

theyre both running https between portal and backend, but content server in prod (where picture upload works) is set to "Standard" security requirement, where as Q/A environment (where picture upload fails) is set to "SSL" security environment. I am afraid this could be the fault? Do you have an opinion on this?

Thanks in advance,

Kind Regards,

Soren

[Former Member · Accepted solution]

Dear Soren,

Yes that could be the change stopping the photo upload - as a normal case since you are creating a repository in the same server and the user credentials in the service to be used for the photo upload - you can change the setting to "Standard"

In case of a SSL, we need to configure different settings for the access of the content repository - in that case we do not need the user ID password to be mentioned for the service.

Please try changing the setting from "SSL" to "Standard" and check the upload.

Thank you

Regards,

Vineeth

[Former Member · Accepted solution]

Hi Vineeth,

I tried to change it to "Standard" setting, but it resulted in http error 401 instead of 403.

Ill keep looking

Thanks,

Kind Regards,

Soren

[Former Member]

Hi Gurus:

My case is that i'm on the middle of the upload (half of the photos been uploaded already) and then the problem Pops-Up! :

HTTP Error: 403 Forbidden

Please help me on this. Thank you.

[Former Member]

Hi Guys,

I reconfigured the content server to "standard" instead of SSL, and found out that the password was wrong in the service (http error 401). After this was corrected it worked.

Still it bugs me that I dont know how to make this work with SSL security.

Kind Regards,

Soren

[Former Member]

Hi,

I can see that it is the Windows Filtering Platform which is blocking the file upload. It looks odd tho since its an unexpected user which is trying to write the file - my guess is its the DB owner user account. It isnt a problem on the Live Prod environment, but its also located in another OU in the AD. Is this policy related? As it is Windows Filtering Platform

If anyone has experience on this matter I would love to hear about it

Thanks,

Kind Regards,

Soren