Describe the bug
When starting your own Language/NLU server and using the authentication layer with --authToken, the diagnostic report will not use the configured token from configuration, meaning that it will return a failed 401 status
To Reproduce
Steps to reproduce the behavior:
1 - Start your own language server but use the "./bp lang --authToken 123456789" to set the authentication token
2 - Change the NLU configuration at nlu.json to use the new started language server
3 - Restart your server and check how its going to work correctly but the diagnostic report will return a 401 error
Expected behavior
Success when checking the connection in the diagnostic report
Environment (please complete the following information):
Describe the bug When starting your own Language/NLU server and using the authentication layer with --authToken, the diagnostic report will not use the configured token from configuration, meaning that it will return a failed 401 status
To Reproduce Steps to reproduce the behavior:
1 - Start your own language server but use the "./bp lang --authToken 123456789" to set the authentication token 2 - Change the NLU configuration at nlu.json to use the new started language server
3 - Restart your server and check how its going to work correctly but the diagnostic report will return a 401 error
Expected behavior Success when checking the connection in the diagnostic report
Environment (please complete the following information):