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
In our application we initialize the CAS Client together with calling CAS_GracefullTerminationException::throwInsteadOfExiting() method and then we handle exceptions in our own fashion.
Right now the same exception CAS_GracefullTerminationException is used when the library ends its work and when there is a real error reported by a phpCAS::error() method.
I think it would be helpful for the integrators, to use a different exception for errors reported in the phpCAS::error() method.
The text was updated successfully, but these errors were encountered:
In our application we initialize the CAS Client together with calling
CAS_GracefullTerminationException::throwInsteadOfExiting()
method and then we handle exceptions in our own fashion.Right now the same exception
CAS_GracefullTerminationException
is used when the library ends its work and when there is a real error reported by aphpCAS::error()
method.I think it would be helpful for the integrators, to use a different exception for errors reported in the
phpCAS::error()
method.The text was updated successfully, but these errors were encountered: