Migration error from disallow external
See original GitHub issuehttps://github.com/feathersjs/feathers/issues/849
Was asked to repost this issue here.
After migration to feathers v3 we get error from Auth-management service.
Error: MethodNotAllowed(405): Provider ‘socketio’ can not call ‘create’. (disableMethod)
We use commonHooks.disallow(‘external’) for ‘all’ hooks.before.
Our service:
const authManagement = require('feathers-authentication-management');
const notifier = require('./notifier');
const configUser = require('../user/config');
module.exports = app => authManagement({
notifier: notifier(app).notifier,
service: configUser.namespace,
identifyUserProps: ['username', 'email', 'phone'],
});
Issue Analytics
- State:
- Created 5 years ago
- Comments:16 (4 by maintainers)
Top Results From Across the Web
Troubleshoot migration issues in Exchange hybrid
Troubleshoots issues with mailbox move in hybrid environment.
Read more >Troubleshooting Common Cloud Migration Errors - BitTitan
Error #5: Your Migration Failed Checking These Credentials – Unable to Connect to the Remote Server · A firewall in the environment is...
Read more >Troubleshooting errors and non-migrated entities with the Jira ...
Go to the boards mentioned in the error log · Click on Board → Configure · Under General and Filter → Edit Filter...
Read more >Troubleshoot an AWS DMS Task That Failed With a Foreign ...
Resolution. To resolve this error, either: Disable foreign key constraints; Use Drop tables on target mode. Disable foreign key constraints.
Read more >Data migration service error codes - Google Support
This error indicates one of the following issues: The service account running the Exchange Web Services (EWS) application pool is set up incorrectly....
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
Whenever the client uses feathers-authentication-management, a
create
call is made to its custom service on (default) pathauthManagement
. You say you are disabling all external calls, so this one throws an error.This has nothing to do with migrating to FeathersJS v3. It would not work in v2 either. You cannot disable its service on
create
.Thanks for the update. This’ll be something I’ll ask when others run into issues. +1