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
{{ message }}
This repository has been archived by the owner on Mar 22, 2022. It is now read-only.
Maybe I'm not understanding the code, but it seems that app.get(<something>) fetches from the relevant config file in the /config directory.
In the documentation here, it suggests the name of this config should be 'auth' for the authentication config. In addition, the code in feathers-authentication-local and feathers-authentication-jwt make the assumption that their configs can be fetched using app.get('auth'). However, when using the generator to generate the authentication service:
feathers generate authentication
The config file is modified to have an "authentication" config, not "auth". Is this correct?
The text was updated successfully, but these errors were encountered:
Yes this was changed in the generator but was never updated in the auth modules. I think because the generator is set up to pass the auth configs explicitly this wasn't caught sooner. I have PRs coming.
Maybe I'm not understanding the code, but it seems that
app.get(<something>)
fetches from the relevant config file in the/config
directory.In the documentation here, it suggests the name of this config should be 'auth' for the authentication config. In addition, the code in feathers-authentication-local and feathers-authentication-jwt make the assumption that their configs can be fetched using app.get('auth'). However, when using the generator to generate the authentication service:
feathers generate authentication
The config file is modified to have an "authentication" config, not "auth". Is this correct?
The text was updated successfully, but these errors were encountered: