So you are hacking away, trying to build an integration or what have you, but you hit a snag.
Here are some of the potential errors you may get, and what they mean:
| HTTP Status Code | Details |
|---|
| 403 |
- The NLS account used to generate a token does not have sufficient privileges for the method being invoked.
- For example NLS account, NLSuser1, may not have privileges to view loans. This account is used to generate an auth token and then is used to make a request to
GET /loans/{loan_id}.
- Please review the account privileges in NLS under Securities to resolve this error.
|
| 500 |
- This is an internal server error thrown by either nsp.auth or nsp.api instances.
- Reviewing the log4net log file will provide additional details on the error. If you have the SaaS version of NLS please contact NLS Support.
|
| 404 |
- 404 will be returned when a resource is not found after making a request to the API.
- For example a request can be made to get details about a loan: https://api.nortridgehosting.com/16.0/loans/444
loan_id 444 does not exist in the database.
|
| 401 |
- No token present.
- Token has expired.
- Invalid Token.
|
| Auth Error | Details |
|---|
| Invalid_Scope |
- The scope parameter being passed during a token fetch request is invalid. This could be an issue with the server name or database name value. This could also be an issue with the scope parameter format.
- Licensed version format
Scope: openid api
- SaaS version format
Scope: openid api server:"server_name" db:"database_name"
|
| Invalid_Grant |
- The NLS username and/or password being passed during a token fetch request is invalid.
- There is an issue with the refresh_token value being passed during a refresh token request against the auth server.
|
| Invalid_Client |
- The ClientID or Secret during the token fetch request is invalid.
|
