Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Docs] Steps to run PulseCOT #7

Open
CoryFoy opened this issue May 25, 2024 · 0 comments
Open

[Docs] Steps to run PulseCOT #7

CoryFoy opened this issue May 25, 2024 · 0 comments

Comments

@CoryFoy
Copy link

CoryFoy commented May 25, 2024

For those trying to get started, here's the steps I took:

  1. You have to get your PulsePoint Agency ID. The easiest way I found to do that was to go to web.pulsepoint.com, search for an agency, and then look at the network inspector in your browser to see what agency_id it requests

  2. I changed line 56 in setup.py from package_data= to license_package_data= to get around the name confliction warning

  3. Because I wanted this sent to a TAK server, I created a user on my TAK server and copied over the .pem and .key file into the same directory as I was running pulsecot. Note that you have to make sure you remove the passphrase or you'll get a prompt for the password

  4. PulseCOT wants the config.ini file to look basically like this. You need to replace AGENCY_ID, takserver and clientcert with what yours actually are:

[pulsecot]
AGENCY_IDS=AGENCY_ID
COT_URL=tls://takserver:8089
PYTAK_TLS_CLIENT_CERT=clientcert.pem
PYTAK_TLS_CLIENT_KEY=clientcert.key
PYTAK_TLS_DONT_VERIFY=1

(Note I have the above without the truststore cert, so I have don't verify enabled. You probably want to add in the appropriate configuration)

And viola! I was able to run pulsecot -c config.ini and see events populate locally and on my TAK server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant