Hi all,
I had a quick look and couldn't see any solutions to the issue I'm facing. Today, suddenly, all our integrations have stopped working in our DEV environment. Whenever we test them, we're receiving a 403 Forbidden error and the following message in the body of the result:
"<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>403 Forbidden</title> </head><body> <h1>Forbidden</h1> <p>You don't have permission to access /suite/webapi/... on this server.</p> <p>Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.</p> </body></html> "
As far as I can see all the proper security is setup, and no changes have been made to them since they were last working yesterday. I've also checked the user credentials used in the connected system and the username and password both seem to be correct. If it matters, these integrations connect to API end points we've exposed from the same Appian application.
Any suggestions to what might be causing this?
Thanks
Discussion posts and replies are publicly visible
403 happens due to invalid credential.can you please cross check again the connected system is having proper usernane and password or not. Password may also expire pls have a look on that as well
Thanks for the response. I've checked a couple of times by logging into the account used for the connected system and there's no issues with the password. Whenever it's been a credentials issue before the response has specifically mentioned that the username or password is invalid. Any other ideas what it might be?
Just check security of the intregration object and connected system
For anyone else that finds this - it turned out to be an issue with our whitelisting. We raised a support ticket with Appian who quickly resolved the issue.
Hi, How the issue has been resolved, could you please help
Hi Nikhilaa, as mentioned it was an issue with the whitelisting. We raised a support case with Appian to limit our Appian environments to certain IP ranges which are whitelisted by our organisation. Hope this helps.