Support of feathers 4.0 crow authentication changes
See original GitHub issueSupport of feathers crow authentication changes
The feathersClient will get some internal updates to the authentication part with crow
.
How will the new version be supported?
I tried to already use it, but there are some calls to old functions like:
return feathersClient.passport
.verifyJWT(response.accessToken)
.then(function(payload) {
commit('setPayload', payload)
As feathers is now longer working with passport this part is failing.
Possible fix
Use something like const jwt = await feathersClient.getAccessToken()
and commit its result to the store.
System configuration
"@feathersjs/authentication-client": "^^4.3.0-pre.1",
"@feathersjs/feathers": "^^4.3.0-pre.1",
"feathers-vuex": "^2.0.0-pre.62"
"vue": "^2.6.10",
"vuex": "^3.1.0",
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
Introducing Feathers 4: A framework for real-time apps and ...
Feathers v4 comes with a new, framework-independent authentication mechanism that is more flexible and easier to use. It supports ...
Read more >@feathersjs/configuration: Versions | Openbase
Full version history for @feathersjs/configuration including change logs. ... authentication-oauth: Fix regression with prefix handling in OAuth (#2773) ...
Read more >@feathersjs/feathers | Yarn - Package Manager
Change Log. All notable changes to this project will be documented in this file. See Conventional Commits for commit guidelines.
Read more >Security Bulletin 02 Nov 2022
CVE Number Base Score Reference
CVE‑2021‑32679 8.8 https://nvd.nist.gov/vuln/detail/CVE‑2021‑32679
CVE‑2021‑32688 8.8 https://nvd.nist.gov/vuln/detail/CVE‑2021‑32688
CVE‑2021‑32765 8.8 https://nvd.nist.gov/vuln/detail/CVE‑2021‑32765
Read more >Why after upgrade feathersjs I receive error: MethodNotAllowed
@Daff is this not a Feathers Crow change? i.e. > v4. Only I just hit this when installing v3.3.1 from npm. Am I...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Here’s what I did. When calling
makeAuthPlugin()
I overrodeactions.responseHandler()
with my own custom function. I’m using Auth0 to authenticate on the client side and not using feathers to generate an access token. I needed to add a few properties and custom logic to the auth plugin. My implementation ends up looking something like:I didn’t need to verify or decode the token returned from feathers (which is exactly the same one I sent them from the client) and the new JWTStrategy already sends you back a decoded token by default (I think it’s in
response.authentication.payload
).There’s probably a lot of stuff that’s only relevant to my particular app, but if you’re interested, you can take a look at my implementation here
This is my complete workaround defined in my auth.ts file