Skip to Main Content
InterSystems Ideas

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.

Status Ideas Contest
Categories Documentation
Created by Guest
Created on Jan 22, 2022

Auto-login to restricted documentation (e.g., HealthShare) for orgs/users

Would be a big people pleaser (at least with my org) if each day we accessed HealthShare docs @ docs.intersystems.com we didn't have to login yet again to access contextual help from the Management Portal.

How? (Just a thought off the cuff) Maybe using some of the new OAuth 2.0 Client capabilities in IRIS, it would be possible for an org to get a client ID/secret from the WRC Portal to setup an OAuth 2.0 Client in each of their instances so that when docs is accessed, a URL Parameter could pass in a value that permits the org to have unfettered access (no user login required) to the online documentation. This would still need to create a valid login cookie so if documentation is accessed directly (without clicking on Help within the Management Portal), the user wouldn't need to login at that point either.

Bonus: This OAuth 2.0 Client arrangement could then also be used to securely send data to WRC logs, etc since it would be able to speak 'on behalf' of the org (with appropriate controls of course.) Maybe even download desired kits to a defined filesystem folder. Possibilities are all there.

  • ADMIN RESPONSE
    May 9, 2025

    Thank you for submitting an idea for the Ideas contest. The status changed to "Ideas Contest".

    Please answer the experts' clarifying questions, if any, during the contest and voting period.