Feature(s) impacted
Unable to access forest admin panel after updating the package to 9.3.8
Observed behavior
Got a vulnerability on 8.7.9 package so dumped the version to 9.3.8 from 8.7.9. Unable to acsess the forest admin panel
Expected behavior
As it was working for agent 8.7.9 it should work on agent 9.3.8 as well
Failure Logs
Context
- Environment name: Development
- Agent (forest package) name & version: 9.3.8
- Database type: Mongoose
- Recent changes made on your end if any: Dumped the package version from 8.7.9 to 9.3.8, now I am unable to access the forest admin panel please help me what I am missing?
Hello @Vishnu_Gupta, thanks for reaching out to us
Please find below the documentation detailing the required steps for you to safely migrate to v9 in a mongoose project:
In particular, you will need to make sure that you have upgraded your roles to the new roles system by going through the migration wizard:
Please ensure that this is performed on your side before attempting the migration once more.
If you need any assistance, you may reach out to us.
Regards,
Nicolas
2 Likes
@Nicolas.M I am getting authentication error post migration / upgrade to V9. I have migrated roles and followed all the instructions mentioned in above documents. I am on forest-express-mongoose^9.0.0
Hello Nicolas, After following all the steps for migrate to the role system and v9 upgrade now we are facing issue with authentication.
I also tried resolving with this solution in: Authentication Error - #12 by Anupam_Rana but nothing fruitful came up and still facing the same issue.
can you please help?
Hello, and welcome to our community.
Could you please open up a new topic with more details about your project and errors faced (agent errors, frontend errors etc …), by following the template below:
Feature(s) impacted
Observed behavior
Expected behavior
Failure Logs
Context
- Project name: …
- Team name: …
- Environment name: …
- Agent (forest package) name & version: … (before and after migration)
- Database type: …
- Recent changes made on your end if any: …
You may be facing a different issue.
Thanks