Hi,
We are trying to update JWT from version 4.1.3 to 4.1.4. During the preparation for the component installation, I am receiving a warning about a potential impact on the Social Login Configurator.
Previously, we encountered this issue and decided to wait until the Social Login Configurator was updated. However, due to security updates in the JWT component, we do not want to wait this time. What would be the best approach to proceed from this point onwards? I would like to avoid cloning the application since this only solves half of the problem.
Best regards,
Bart Nooijens
Hi Bart,
If waiting for an update is not an option, you could consider modifying the Social Login Configurator yourself to make it compatible with JWT version 4.1.4. Once you've successfully implemented and tested the changes, you could share your updated version on the Forge as a contribution. This allows the community to validate your changes and helps expedite the patching process.
By doing so, you not only solve your issue but also contribute to improving the component for others facing the same challenge.
Hi @Cristian Angel Puma Villalva,
Thank you for replying!
I think in general this is a good advice and I could absolutely look into it. I did some testing on our environment and updating the component seems to work despite the warning.
What I dislike from this component at the moment is that it is a supported component but a 3rd party component (JWT) is needed to update it properly. In this case JWT has security updates and therefor I think waiting on a update which has security related updates is a bit odd. Should this component depend on a non-supported, made by the community component? It's food for thought.
Bart