FOUR-30920: Remove expected DevLink ping 401

[eiresendez]

Issue & Reproduction Steps

Creating a new DevLink currently stores the local DevLink record and then calls GET /api/1.0/devlink/{id}/ping before OAuth has completed. Because the DevLink does not have a usable access token yet, the ping returns a browser-visible 401 even though the flow is expected to continue to the remote OAuth/login step.

To reproduce:

1. Log in as an admin.
2. Go to Admin > DevLink.
3. Create a new DevLink using a local or remote ProcessMaker URL.
4. Observe that the flow redirects to OAuth/login correctly, but the browser console/network panel shows a 401 for the ping request.

Solution

• Normalize DevLink ping responses into semantic statuses: ok, authorization_required, or error.
• Return HTTP 200 for expected remote authorization failures so the browser no longer shows a false 401 during the happy path.
• Update the Create DevLink flow to redirect for ok and authorization_required, and show the existing error state only for real failures.
• Add focused API coverage for successful ping, unauthorized/forbidden remote responses, server failure, and connection failure.

How to Test

• vendor/bin/phpunit tests/Feature/Api/DevLinkTest.php --filter Ping
• vendor/bin/phpunit tests/Feature/Api/DevLinkTest.php
• npm run development

Manual check:

1. Create a new DevLink.
2. Confirm the flow still redirects to the remote OAuth/login step.
3. Confirm the local ping request no longer returns a browser-visible 401 during the expected pre-authorization path.

Related Tickets & Packages

• https://processmaker.atlassian.net/browse/FOUR-30920

ci:deploy

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[vladyrichter]

QA server K8S was successfully deployed https://ci-09ba128f9d.engk8s.processmaker.net

[CarliPinell]

Approved.
No observations found