-
Notifications
You must be signed in to change notification settings - Fork 561
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MeshCentral fails to start with openid-client v6.0.0 #6459
Comments
i was literally just about to post this issue! |
fix for the moment is here
|
the same on my end. I have MC installed in podman container and currently with oidc it fails to start:
I've worked around it for the time being by mapping the |
@Pshemas, yes, it has already been pinned/fixed in the We just need to do a new release next month to have it fully included. Or do the steps above |
After a careful reading it seems my error is different. On my end npm was not able to install those extra packages (apart from openid it was also passport and one more package) inside containers. The first thing I've tried was getting into the container (interactive bash session) and launching the commands manually. It failed too. Checked the connection - it was fine (I could access npm repo site from container). So in the end I've mapped the folder where the dependencies are kept and installed those using npm on the host system. |
Describe the bug
openid-client released version 6.0.0 two days ago as an ESM module, which causes MeshCentral to fail to start (if openid authentication is enabled)
See
https://github.com/TypeStrong/ts-node#err_require_esm
https://github.com/panva/openid-client/releases/tag/v6.0.0
To Reproduce
Steps to reproduce the behavior:
Expected behavior
MeshCentral starts and has the OIDC login button.
Screenshots
N/A
Server Software (please complete the following information):
Client Device (please complete the following information):
N/A
Remote Device (please complete the following information):
N/A
Additional context
Your config.json file
The text was updated successfully, but these errors were encountered: