ATNA repository

[vaclav...@gmail.com]

Hi everyone,

I am using dcm4chee 5.12.0 and would like to have an ATNA repository. I have seen from this post that the ATNA audit logs are available. But I don't know how to set up the repository. 

I found this installation for an audit record repository but I also noticed that I already have an ARR in my dcm4chee in the device "logstash" it is called syslog and the adress is localhost:514. 

Do I still need to complete the installation of the ARR ? 

Thanks a lot for answers !

Vaclav

[vaclav...@gmail.com]

So, I realized some things about my previous post, I looked at the configurations : https://github.com/dcm4che/dcm4chee-arc-light/wiki/Audit-Logger and https://github.com/dcm4che/dcm4chee-arc-light/wiki/Audit-Record-Repository. Everything is OK so I doubt I have to do the ARR installation as mentionned in the above post.

But I still don't know how to access the audit messages... 

[Gunter Zeilinger]

dcm4chee-arc 5.x just emits Audit Messages according IHE ATNA. You may use Elastic Stack as Audit Record Repository. s. https://github.com/dcm4che/dcm4chee-arc-light/wiki/Run-secured-archive-services-and-Elastic-Stack-on-a-single-host

On Thu, Jul 26, 2018 at 1:38 PM, <vaclav...@gmail.com> wrote:

So, I realized some things about my previous post, I looked at the configurations : https://github.com/dcm4che/dcm4chee-arc-light/wiki/Audit-Logger and https://github.com/dcm4che/dcm4chee-arc-light/wiki/Audit-Record-Repository. Everything is OK. 

But I still don't know how to access the audit messages... 

--
You received this message because you are subscribed to the Google Groups "dcm4che" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+unsubscribe@googlegroups.com.
To post to this group, send email to dcm...@googlegroups.com.
Visit this group at https://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/d/optout.

[vaclav...@gmail.com]

Hello Gunterze,

Thanks for your answer it is exactly what I needed. I just have one last question : at the beginnig there is this sentence

"Ensure that there is a hostname entry in your DNS server for the docker host."

I don't know how to do that, I checked on google but didn't find anything that would tell me what the hostname entry for the docker host is. 

So I tried with localhost but I guess it is wrong because at some point I try to access https://localhost:8843/auth/admin/dcm4che/console and it doesn't work.

Do you know how to figure out the hostname ? (sorry the question isn't really about dcm4chee...)

Thank you !

[Gunter Zeilinger]

It's not a must, but it simplifies the configuration of the docker containers, if the host name of the node, on which you run the docker engine, is resolvable inside of the containers. E.g. on Linux, the own host name is typically mapped in /etc/hosts to 127.0.0.1, so it will not work if a container resolve that host name to 127.0.0.1, because that points to the loop back address of the docker container and not of the docker host, so the container cannot connect to a port exported to the docker host from another container.

--

[vaclav...@gmail.com]

Thank you for your answer Gunterze, i do understand why it couldn't work with localhost. 

On docker I ran the command : ifconfig it showed me this

So I tried to use docker0 and eth0 as the <docker-host> but it won't even create the containers. 

Then I tried with the inet addr, the containers can be created but when I try to access https://inet_addr:8843/auth/admin/dcm4che/console

I get error_connection_timed_out

I don't know what else I could try now... 

Also I do have another question, if it worked would I have been able to access the logs at this adress https://inet_addr:8843/auth/admin/dcm4che/console ? 

Thank you so much for your time !

Vaclav

[gunterze]

On Linux, you just need to adjust /etc/hosts to map your IP instead of 127.0.1.1 to your host name and replace <docker-host> in ENV AUTH_SERVER_URL=https://<docker-host>:8843/auth by your host name.

Audit and System logs can be browsed using Kibana. In the sample docker-compose.yml, the kibana port 5601 is not mapped out from the container, to secure its access via the keycloak-proxy, listening on port 8601 (http) and 8643 (https).

[vaclav...@gmail.com]

Ok I get it now ! 

Thanks a lot Gunter !