500 Error when editing Project | Community
Skip to main content
Level 2
November 5, 2024
Solved

500 Error when editing Project

  • November 5, 2024
  • 1 reply
  • 918 views

We currently have a project setup for as part of our user sync from on-prem AD - and we need to edit this to complete the JWT to OAuth migration. However, for the last few days we've been having a 500 error (see screenshot) when we open the project, and the JWT credential tab is missing.

 

Not sure if this is a transient error on your side and we just need to wait, or if there is an issue with our project? Can we just re-create this with new OAuth creds instead if necessary?

 

Thanks.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by tmj

Hey, @MatthewBe15, did you find out if the issue is transient? If not, could you send a full-screen screen recording of the problem you're still seeing? 

 

Please don't include any secrets or sensitive information in the recording. If you're not comfortable sharing the details on the forum, you can start a support case with Adobe through your regular channels.

 

Thanks
Manik

1 reply

tmj
Adobe Employee
tmjAdobe EmployeeAccepted solution
Adobe Employee
November 5, 2024

Hey, @MatthewBe15, did you find out if the issue is transient? If not, could you send a full-screen screen recording of the problem you're still seeing? 

 

Please don't include any secrets or sensitive information in the recording. If you're not comfortable sharing the details on the forum, you can start a support case with Adobe through your regular channels.

 

Thanks
Manik

Level 2
November 5, 2024

Thanks Manik - it's been happening for a few days, so suspect it's an issue just for our project. I can't do a screen recording, but it's quite straightforward to show in a couple of screenshots.

Screenshot 1 shows our project in the portal, with "attention required" - then when we click on it, it takes us to the project page which I've shown in screenshot 2 with the error.

We appear to be missing the options on the left required to move to OAuth that the notes suggest should be there.

Thanks.