Thank you. We are definitely going to use an authorization server. Thank you very much.

I will keep an eye on the issue on GitHub.

Thank you very much.

Thank you for your reply. We were looking at it as an option because jsreport does not check password strength and it was bothering us. At least if we could stop users from changing the password that could have been a good security. Is there a way we can enforce password strength? We have noticed an admin can add a user with a password as simple as 123 or 12. Is there a way we can ask admin for stronger password?

Thank you.

Hello,
I am an admin, and I have created a user X with password Y. When user X logs in they are able to change their password from Y to Z since there is a "change password" option in the setting. However, I do not want user X to be able to change their password, only admin (myself) can change user X's password. How can I stop user X from changing their password? is it even possible?

Thank you.

Thank you @bjrmatos This actually worked.

@ThomasJReiter Thank you very much for your response. I am running jsreport in docker.

I am gonna try your approach and give a feedback.

After building the image and starting my container everything is working fine.

I then wanted to mount my jsreport so my changes reflect direclty to the vscode and vise verse.

here is the command: ./dev-mnt-jsreport.sh

As soon as I ran this command I started having the error below:

2022-02-11T21:33:14.400Z - error: Error occurred during reporter init: Error: Error when loading extension fs-store@3.1.0

Error: EACCES: permission denied, mkdir '/data/storage'

at Object.mkdirSync (node:fs:1334:3)

at module.exports (/app/node_modules/@jsreport/jsreport-fs-store/lib/blobStorageProvider.js:8:8)

at Object.module.exports (/app/node_modules/@jsreport/jsreport-fs-store/lib/main.js:37:75)

at Object._useOne (/app/node_modules/@jsreport/jsreport-core/lib/main/extensions/extensionsManager.js:226:75)

at Object._useMany (/app/node_modules/@jsreport/jsreport-core/lib/main/extensions/extensionsManager.js:99:38)

at async MainReporter.init (/app/node_modules/@jsreport/jsreport-core/lib/main/reporter.js:199:7)

at Object._useOne (/app/node_modules/@jsreport/jsreport-core/lib/main/extensions/extensionsManager.js:248:15)

at Object._useMany (/app/node_modules/@jsreport/jsreport-core/lib/main/extensions/extensionsManager.js:99:38)

at async MainReporter.init (/app/node_modules/@jsreport/jsreport-core/lib/main/reporter.js:199:7)

Error: Error when loading extension fs-store@3.1.0

Error: EACCES: permission denied, mkdir '/data/storage'

at Object.mkdirSync (node:fs:1334:3)

at module.exports (/app/node_modules/@jsreport/jsreport-fs-store/lib/blobStorageProvider.js:8:8)

at Object.module.exports (/app/node_modules/@jsreport/jsreport-fs-store/lib/main.js:37:75)

at Object._useOne (/app/node_modules/@jsreport/jsreport-core/lib/main/extensions/extensionsManager.js:226:75)

at Object._useMany (/app/node_modules/@jsreport/jsreport-core/lib/main/extensions/extensionsManager.js:99:38)

at async MainReporter.init (/app/node_modules/@jsreport/jsreport-core/lib/main/reporter.js:199:7)

at Object._useOne (/app/node_modules/@jsreport/jsreport-core/lib/main/extensions/extensionsManager.js:248:15)

at Object._useMany (/app/node_modules/@jsreport/jsreport-core/lib/main/extensions/extensionsManager.js:99:38)

at async MainReporter.init (/app/node_modules/@jsreport/jsreport-core/lib/main/reporter.js:199:7)

And the container keeps restarting.

I know it has to do with permission but since i am new I am a bit confused.

I am using WSL2

Thanks for your help.

Hello,
When running JSReport to a new Tab, we do not have the logout button. Does Anyone know how one can replicate jsreport logout button?

In details:

We send our non-tech user a link to view different report. This is what they see when they click on the link. We want a logout button for them to end a session when they are done with the reports. Basically the same logout as the one jsreport has.

The first idea was the clean the cookie on click. However, the cookie is HTTPOnly so we cannot access it, edit or clear.

Is there a way we can achieve this? Or is there other solutions you can suggest?

Thank you.