question Re: How to set basic auth on headers in oozie workflow callback url. in Archives of Support Questions (Read Only)

How to set basic auth on headers in oozie workflow callback url.

vikram_nanjunda — Fri, 02 Dec 2016 02:18:02 GMT

oozie.wf.workflow.notification.url=http://yourserver.com/some/path/

In oozie job.properties we can include this property to get workflow notification. In our use case we have the callback url (rest service) which requires basic auth. Is it possible to set basic auth in the header when oozie calls back this url ? If so can you point me to the documentation. Thanks.

Re: How to set basic auth on headers in oozie workflow callback url.

VR46 — Sat, 03 Dec 2016 22:54:07 GMT

Hello @Vikram,

I looked into Oozie workflow spefification here and source code here to check how this URL is handled. As mentioned in the documentation, Oozie just makes a get request to "oozie.wf.workflow.notification.url" URL. This means, as long as you can specify a fully qualified URL with required basic authentication info (maybe via query-string and token), Oozie should be able to deliver that.

Hope this helps.

Re: How to set basic auth on headers in oozie workflow callback url.

KuldeepK — Fri, 09 Dec 2016 17:57:28 GMT

Customer confirmed that this worked.

Re: How to set basic auth on headers in oozie workflow callback url.

tejwinder91 — Sat, 28 Jan 2017 02:37:28 GMT

I am using this oozie.wf.workflow.notification.url property but I am facing an issue :

https://myknoxurl:8443/gateway/default/myproject/services/job/?user.name=tejwinder_singh

I am using knox to connect to remote tomcat (which will capture oozie's statuses)

How do I add my password to the URL ? Or Is there a better solution to do this via Knox ?