It looks like indeed lumber does not support SSL certificates when generating a project. I’ll turn this need into a feature request. Thank you for outlining that missing feature!
However, by design, ForestAdmin is built to generate a local version of your admin panel first, plugged onto a local database. Then you create a production environment that you plug onto your production database.
This means that in your case, you should (and that’s supposed to be the preferred way) have a local copy of your production database (ideally with a lighter and anonymised content), on which you would generate your project using lumber. Then, when putting this development project into production, you’d be able to edit the sequelize connection defined in the
models/index.js file to include your ssl certificates (as described here for example)