403 Error post Utha upgrade glide-utah-12-21-2022__patch5-07-06-2023 on Rest API Post Method

[Rashmika BS]

Hi Team, 

We are receiving an error while testing a Rest API post method post Utha upgrade. 

Method failed: (/***) with code:403 - Forbidden username/password combo

AUth profile has correct details. Mid server is up and running. Yet we are getting this issue.

Thanks

[Prabu Velayutha]

@Rashmika BS  Are you posting to the third party rest API end point through Rest Message or Flow Action? is it basic auth or oauth? is this on production instance or non prod? if non prod is that cloned recently after upgrade if so create a new auth profile with the credentials and try again.  

Is the auth profile and rest API connection working on lower instance with same credentials?

[Rashmika BS]

Yes, we are using post method on third party. Yes the same account works fine in Dev instance and not in qA. Yes, we did utha upgrade before that we did cloning from prod. 

[Prabu Velayutha]

@Rashmika BS did it work post cloning? is this configured in production too?

verify if your using the Dev or QA or Prod base API end point url for connection. If you know the credentials try recreating a new auth profile. If these table are not excluded from cloning they will get cloned so the connection URLs and credentials would get impacted. 

If my response helps to solve your issue. Kindly mark it as helpful & correct. It will be helpful for future readers!  

[Rashmika BS]

I m not sure if it worked post cloning but the mid server details I had to update post cloning and upgrade. I tried creating new aunty profile and yet I get the same error.