All
Accepted answers
Sergei Shutov · Mar 18 go to post

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.

Sergei Shutov · Apr 16 go to post

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

Sergei Shutov · Apr 17 go to post

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.

Sergei Shutov · Apr 17 go to post

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

Sergei Shutov · Apr 22 go to post

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!

Sergei Shutov · Oct 13 go to post

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