You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the only way to disable this is to make workarounds using buffering or modifying library using composer-patches.
Users may want to handle errors in their own fashion, and displaying messages directly is not a good way to do it.
As a partial solution for first case it could be do like so:
but it does not solve $client->printHTMLHeader($lang->getAuthenticationFailed()); line and second case.
In my opinion phpCAS should offer some way (preferably config option) to disable writing error messages directly to the response.
The text was updated successfully, but these errors were encountered:
Magiczne
changed the title
No ability to disable displaying errors to the screen.
No ability to disable displaying errors directly into the response.
Jul 7, 2021
The issues You have pointed out are 7 and 9 years old respectively.
I could try to make PR with simple configuration variable to turn off the messages i have pointed ouy, but making logging modular is out of my scope right now.
Right now, there are places in the library where error messages are displayed directly into the response, mainly:
Right now the only way to disable this is to make workarounds using buffering or modifying library using composer-patches.
Users may want to handle errors in their own fashion, and displaying messages directly is not a good way to do it.
As a partial solution for first case it could be do like so:
but it does not solve
$client->printHTMLHeader($lang->getAuthenticationFailed());
line and second case.In my opinion phpCAS should offer some way (preferably config option) to disable writing error messages directly to the response.
The text was updated successfully, but these errors were encountered: