Rechercher

Discussion (4)3
Connectez-vous ou inscrivez-vous pour continuer
Discussion (4)2
Connectez-vous ou inscrivez-vous pour continuer
Question
· Oct 29, 2024

git-source-control configuration for remote development

#Git #InterSystems IRIS for Health

How do you configure it to have source control on a namespace accessed via the InterSystems Server Manager extension?

An example from the video explains only how it will work with a cloned git repo on a local machine (PC/Mac), but so far, I can't get it to work on a remote development server (replacing existing remote Studio via RDP with local VS Code).

2 Comments
Discussion (2)3
Connectez-vous ou inscrivez-vous pour continuer
Annonce
· Oct 29, 2024

[Video] Securing AI Implementations - Moving from Experimentation to Production

#Artificial Intelligence (AI) #Global Summit 2024 #Large Language Model (LLM) #Vidéo #Summit

Hey Community,

Watch the new video on InterSystems Developers YouTube:

⏯ Securing AI Implementations - Moving from Experimentation to Production @ Global Summit 2024

As AI systems transition to full-scale production environments, their security demands not only traditional cybersecurity best practices (such as good access controls and authentication mechanisms), but also specialized protections tailored to AI technologies. Key among these is maintaining an inventory of AI usage (comprehensive AI Bills of Materials (AI-BOMs) that enumerate all components of AI systems), robust logging practices, and continuous monitoring of prompts, and inference results to swiftly identify and mitigate potential security threats. This presentation will cover the top security risks facing Large Language Model (LLM) implementations, with a focus on protecting sensitive data and proprietary information. We will discuss a few industry-wide initiatives and highlight best practices in securing AI systems, Retrieval Augmented Generation (RAG) implementations, and the "LLM stack".

🗣 Presenter: Omar Santos, Distinguished Engineer, Cisco

Enjoy watching, and expect more videos! 👍

2 Comments
Discussion (2)2
Connectez-vous ou inscrivez-vous pour continuer
Question
· Oct 29, 2024

How to configure local IPM registry authorization?

#InterSystems Package Manager (IPM) #InterSystems IRIS for Health

I'm working on my first (!) IPM module and I'm a little puzzled with the registry authorization.

I have a working local registry (I hope!) and the module is loaded (with load-command) to the namespace.

Now publish-command fails because of missing authorization. I have set nothing authorization related myself and I'm lost how the authorization should be configured. All the material I have read so far seems to ignore that and only mentions one have to authenticate ...

Here's the command output:

zpm:IPMTEST1>version

%SYS>     zpm          0.7.3
IPMTEST1> zpm-registry 1.3.2
https://pm.community.intersystems.com - 1.0.6
http://localhost:52773/registry/ - 1.3.2

zpm:IPMTEST1>list-installed -tree
osex-ipm-demo 1.0.0
├──osex-ipm-hello 1.0.0
└──osex-ipm-numbers 1.0.0
zpm-registry 1.3.2
└──yaml-utils 0.1.4

zpm:IPMTEST1>publish -verbose osex-ipm-hello

[IPMTEST1|osex-ipm-hello]       Reload START (/home/irisowner/work/objectscript-ex/ipm/hello/)
Skipping preload - directory does not exist.
Load of directory started on 10/29/2024 19:14:29 '*'

Loading file /home/irisowner/work/objectscript-ex/ipm/hello/src/OSEX/ipm/hello/Hello.cls as udl
Load finished successfully.

[IPMTEST1|osex-ipm-hello]       Reload SUCCESS
[osex-ipm-hello]        Module object refreshed.
[IPMTEST1|osex-ipm-hello]       Validate START
[IPMTEST1|osex-ipm-hello]       Validate SUCCESS
[IPMTEST1|osex-ipm-hello]       Compile START
Compilation started on 10/29/2024 19:14:29 with qualifiers 'd-lck'
Compiling class OSEX.ipm.hello.Hello
Compiling routine OSEX.ipm.hello.Hello.1
Compilation finished successfully in 0.007s.

[IPMTEST1|osex-ipm-hello]       Compile SUCCESS
[IPMTEST1|osex-ipm-hello]       Activate START
[IPMTEST1|osex-ipm-hello]       Configure START
[IPMTEST1|osex-ipm-hello]       Configure SUCCESS
Studio project created/updated: osex-ipm-hello.PRJ
[IPMTEST1|osex-ipm-hello]       Activate SUCCESS
[IPMTEST1|osex-ipm-hello]       Package START
Exporting 'OSEX.ipm.hello.Hello.cls' to '/usr/irissys/mgr/Temp/dirfi49Wp/osex-ipm-hello-1.0.0/src/OSEX/ipm/hello/Hello.cls'
Exported to /usr/irissys/mgr/Temp/dirfi49Wp/osex-ipm-hello-1.0.0/module.xml
Module exported to:
        /usr/irissys/mgr/Temp/dirfi49Wp/osex-ipm-hello-1.0.0/

Module package generated:
        /usr/irissys/mgr/Temp/dirfi49Wp/osex-ipm-hello-1.0.0.tgz
[IPMTEST1|osex-ipm-hello]       Package SUCCESS
[IPMTEST1|osex-ipm-hello]       Register START
[IPMTEST1|osex-ipm-hello]       Register SUCCESS
[IPMTEST1|osex-ipm-hello]       Publish START
Publish to: http://localhost:52773/registry/
[osex-ipm-hello]        Publish FAILURE
ERROR! Publishing module, authorization required.
zpm:IPMTEST1>
6 Comments
Discussion (6)2
Connectez-vous ou inscrivez-vous pour continuer