OAuth - Internal Error

BIZ TMS Sphinx
1

There is an account on the system which, when the user tries to login, generates this error

FJSError
: 
Error: OAuth error: server_error - Internal server error: IbRD4JUblVF9Zbedg-FW3EiJx-S3BCDVfYE81c3cn14 at Object.Create$1

and leaves the user with a blank screen.

  1. do you know what that error code refers to?
  2. is it possible for Sphinx to handle catastrophic errors more elegantly?

Thanks

2

When you have a logging middleware, any 5xx error raised by the server are responded like that for security reasons. The client only receives an "internal server error", and the real error is logged as a trace message. Make sure you log trace messages to some place (like a text file) to see what the message refers to.

I'm not sure it can be more elegant than this. What is your suggestion?

3

Thanks, I'll look in the logs.

Not just a blank screen.

Some message that there was a problem? Give them to log in with another account?

4

The internal error is really an "internal" error. It's an unhandled error at your side. It's usually not safe to tell the customer what it is. Might be a wrong SQL, disk issues, whatever. It also really depends on the moment of the error. It's not clear here when does it happen.

5

It happens when the password is submitted.

I wasn't thinking that they are given error details, just not left with an empty browser window.

6

Do you have a link about how to get the middleware to write to a file? I'm sure I've done this before, but can't find it. thanks

7

Here: Middleware System | TMS Sparkle documentation and here: Logging | TMS Sparkle documentation.

And, of course, here: Output Handlers | TMS Logging documentation

There are also three logging demos in Sparkle, in folder demos\logging.

1 Like