Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,473
Community Members
 
Community Events
176
Community Groups

OEC Proxy Authentication

Our IT security team is mandating all outbound connections through our proxy servers should be authenticated (BasicAuth or NTLM). I'm not seeing anything in the OEC setup docs about adding this authentication. Has anybody gotten this working?

1 answer

0 votes

Hi Tom!

 

Justin here, from Opsgenie support - happy to help!

 

You should be able to your proxy configuration (with authentication) in the environment variables defined in the OEC service file. So, for basic auth, it might look something like this (examples below for both Windows and Linux OEC service files):

 

Windows

Filename: oecService.json

You can add the HTTP_PROXY and HTTPS_PROXY values with authentication in the 'Env' field in the oecService.json file.

{
"Name": "OEC Service",
"DisplayName": "OEC Service",
"Description": "Run the OEC Service",
"OECPath" : "C:\\opsgenie\\opsgenie-oec\\OpsgenieEdgeConnector32.exe",
"Args" : ["-oec-metrics", "7070"],
"Env": [
"OEC_CONF_LOCAL_FILEPATH=C:\\opsgenie\\opsgenie-oec\\conf\\config.json",
"OEC_CONF_SOURCE_TYPE=local",
"HTTP_PROXY=http://user:password@ProxyServer:port",
"HTTPS_PROXY=http://user:password@ProxyServer:port"
],
"Stderr": "C:\\opsgenie\\opsgenie-oec\\output\\oecErr.log",
"Stdout": "C:\\opsgenie\\opsgenie-oec\\output\\oecOut.log"
}

 

Note - if OEC is already installed then you will need to reinstall OEC. The uninstall command (adjust accordingly for 32 or 64 bit OEC) is:

 oecService<32|64>.exe uninstall 

the install command is:

 oecService<32|64>.exe install

 

 

Linux

Filename: oec.service

You'll add your HTTP/HTTPS_PROXY info as Environment variables called out in the oec.service file:

[Service]
Group=opsgenie
User=opsgenie
Type=simple
Environment="HTTP_PROXY=http://user:password@ProxyServer:port"
Environment="HTTPS_PROXY=http://user:password@ProxyServer:port"
ExecStart=/usr/local/bin/OpsgenieEdgeConnector

 

Once these have been added, you'll need to reload and restart the service:

systemctl daemon-reload
systemctl restart oec.service

 

 

That should get you started, but please let us know if you have any issues getting the proxy working. Thanks!

 

Justin S

Atlassian Cloud Support

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS

Atlassian Community Events