oberstet
commented
2 years ago Crossbar should take care of this when worker is started.
Authenticators, like everything else in Crossbar.io, are dynamic server resources with their own lifetime. Resources are hence initialized when they come into existance - which might be during node startup, or any time later (!)
IOW: won't fix
When using dynamic authenticator of
"type": "function", the authenticator code is not initialized on worker startup. Instead the authenticator is setup when the first client tries to connect. This is fine in general but can be problematic when developing application code as even a broken import can be missed.Crossbar should take care of this when worker is started.