Hi,
We may have found an issue with the authenticated custom entry point. It seems that there is an issue with the authentication even when the user is already logged in. We have experienced this on our custom entry points after we upgraded sugar to 12.0.1 Enterprise from 10.0.4 Professional. This used to work before the upgrade.
To simplify the explanation, we have created the custom entry point and replicated the issue on a fresh sugar 12.0.1 Enterprise instance (SugarCRM Version 12.0.1 (Build 298 E) (Q2 2022)) and just used the example on creating custom entry points from the Sugar developer guide. Here are the steps we followed to replicate the issue:
1. Login to Sugar
2. Add custom entry point as instructed in the example here - https://support.sugarcrm.com/Documentation/Sugar_Developer/Sugar_Developer_Guide_11.0/Architecture/Entry_Points/Creating_Custom_Entry_Points/
3. Navigate to http://{sugar url}/index.php?entryPoint=customEntryPoint (on this step, custom entry point is working fine)
4. Log out of Sugar.
5. Login to Sugar.
6. Navigate to http://{sugar url}/index.php?entryPoint=customEntryPoint - This will redirect you to home page which should have been the custom entry point page.
Note: After the steps above, doing a QRR appears to solve the issue, custom entry point will work again temporarily. Logging out and logging in will cause the custom entry point to redirect to the home page again.
There were no errors on sugarcrm.log file and no errors on apache when navigating to the custom entry point link. Network tab shows status code 302 found on the request.
Is this a known bug? Are there any solutions or workarounds for this? Thank you.
John Patrick Pepito |
