Have an idea, suggestion, or something that doesn’t work as expected in InterSystems products or services? Share it here on the InterSystems Ideas Portal.
The Ideas Portal is where community members can propose improvements, report bugs, and help influence the product roadmap across InterSystems products and the overall developer experience. 22% of submitted ideas are implemented by InterSystems or members of the Developer Community.
💡 Ideas and bugs are both welcome, no matter how big or small. You can submit feature requests, usability improvements, workflow suggestions, and bug reports. Whether you’re an experienced expert or just getting started, your fresh perspective is valuable.
🛠️ About bugs and fixes. If you have access to InterSystems WRC, please submit bugs there for immediate action. Bug reports submitted through the Ideas Portal are reviewed and tracked, but do not guarantee immediate resolution.
Start by sharing what could be better - the community and our teams will help take it from there.
And even so, I see no reasons of using PasswordHash at all, in any scenarios, for me it looks like completely useless idea, and also for some reasons, InterSystems decided to deliver this tool separately only as a docker image.
When the world goes one way, IRIS looks like lives in another universe, with a different rules, and developers should find a ways, how to fit it here
we can discuss on DC
https://community.intersystems.com/post/iris-service-continuous-integration
How PasswordHash will help?
I need to run vanilla docker image with IRIS, in a cloud environment, where I have almost no control, only docker image name, and can pass environment variables, that's it
You mean, use some one more external image, to generate hash, and how I would use it?
I understand the convenience with environment variable, but why PasswordHash is not enough?