go to post Sergei Shutov · Oct 13 Yes you absolutely don't want to hard code those in the code. You have two options: 1) have a login form which will ask for those and save them in either local variables (will have to enter login password after each page refresh) or local storage (not secure because password is available in plain text). You can try some silly endpoint like _ping to check if it returns 200 or 403 to check if credentials are valid. 2) use web sessions and store session information in cookies. Here you can use usual iris login page to authenticate, but it's not rest best practices because use of session is discouraged Or 3) set up and implement jwt authentication as described in documentation https://docs.intersystems.com/iris20242/csp/docbook/DocBook.UI.Page.cls?... I'd say from my experience, best for security and production use is 3, most people implement 2, and 1 is only good for prototyping/experiments because it's not secure
go to post Sergei Shutov · Apr 22 That's an ambitious plan for sure! I also recommend the demos&drinks event, you can learn a lot of stuff you don't even have an idea you wanted to know about before you see it :) . See you there!
go to post Sergei Shutov · Apr 17 1) Download and install docker 2) Run this code in terminal docker run --rm --name iris-demo -d -p 9090:52773 -e IRIS_USERNAME=demo -e IRIS_PASSWORD=demo intersystemsdc/irishealth-community:latest 3) Open browser at http://localhost:9090/csp/sys/UtilHome.csp and use VSCode to connect to the same host/port Regarding SQL Server setup, you'll have to ask on SQL Server forum
go to post Sergei Shutov · Apr 17 I'm with Tim on this one, it's OK to create something like https://sergeinator.com for fun and giggles or use is as a prototyping tool instead of MS Paint, but I would not let this code anywhere near production.
go to post Sergei Shutov · Apr 16 Great article Tim! I think another area where AI can help a lot and which is usually overlooked in IRIS development is an automated testing
go to post Sergei Shutov · Mar 18 Looks like the error is on a back-end, the Java code you are calling is not configured properly. Try running it from the terminal.
go to post Sergei Shutov · Mar 18 There is an unattended restore routine https://docs.intersystems.com/iris20243/csp/docbook/DocBook.UI.Page.cls?...
go to post Sergei Shutov · Feb 25 Which means that Colin guessed the code right and no, trace is not computed when tracing is off :)
go to post Sergei Shutov · Feb 4 Hi Stephen, this is a valid approach however you will lose information about problematic calls such as json can't be parsed or API key in headers is wrong. I prefer to actually save the http call in full as http generic message and then call a process or operation with transformation to the proper message format, as Alex demonstrated in his third example. You can still call operation manually if you want, passing the parsed message.
go to post Sergei Shutov · Dec 12, 2024 Yes you can use $system.Encryption.TOTPValidate() function https://docs.intersystems.com/iris20243/csp/documatic/%25CSP.Documatic.c... See also https://community.intersystems.com/post/systemencryptiontotp-synchroniza...
go to post Sergei Shutov · Dec 12, 2024 Is there a list of changes? Release notes document looks very empty https://docs.intersystems.com/iris20251/csp/docbook/DocBook.UI.Page.cls?...
go to post Sergei Shutov · Aug 5, 2024 Congratulations to all winners, it was difficult to vote this time, so many great applications and samples!
go to post Sergei Shutov · Apr 6, 2024 Hi @Alex Woodhead there is no "preview" container on the https://containers.intersystems.com site any more, only "latest-preview" - was this released? If so which build? Thanks! =Sergei
go to post Sergei Shutov · Feb 4, 2024 Hi @Evgeny Shvarov You need to use port 52773 with localhost in Docker. It's relative to the container not to your host. I just tried this with intersystemsdc/irishealth-community:latest image above, works fine.
go to post Sergei Shutov · Feb 4, 2024 Looks like a typo, this one works: https://iris-fhirfy.demo.community.intersystems.com/csp/fhirfy/index.html
go to post Sergei Shutov · Feb 4, 2024 Ciao Henry, this URL doesn't open for me can you double check?
go to post Sergei Shutov · Nov 14, 2023 Yes but you can have one top-level 'manually created' one and have individual ones based on separate OpenAPI files
go to post Sergei Shutov · Jul 12, 2023 Well you gave me two so I should have one spare wish :) Make iris:latest-cd just iris:latest, this way we can just skip the "latest" bit altogether and just use iris without any tag at all.
go to post Sergei Shutov · Jul 3, 2023 Hi Bob, That's good news and I like new names much more than old ones. I hope old tags for old releases will still be available? A couple of entries from my container tagging wishlist (one can dream, you know) - provide :latest tag for all containers, but especially for community ones, which will just pull the latest working release without having to rebuild dockerfiles every year when license expires - provide 2023.1.x tag which will follow the latest minor version
