Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

obscure error if jwtSecret isn't configured #3

Open
pekeler opened this issue Jan 30, 2016 · 1 comment
Open

obscure error if jwtSecret isn't configured #3

pekeler opened this issue Jan 30, 2016 · 1 comment
Assignees
Labels

Comments

@pekeler
Copy link

pekeler commented Jan 30, 2016

I think it would be good if this app threw an explicit error telling me that this value is missing, instead of this obscure stack trace: arangodb/arangodb#1696

@pluma
Copy link
Contributor

pluma commented Jan 30, 2016

Indeed. The problem is that the secret is not required because the "none" type encryption must not use a secret whereas every other type must use a secret. Therefore we can't rely on the app not being mounted unless properly configured and instead need to catch misconfiguration at runtime.

@pluma pluma added the bug label Jan 30, 2016
@pluma pluma self-assigned this Jan 30, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants