HTTP Authentication?

[Antonio García Domínguez]

Hi everyone,

For my current line of work, I need to authenticate into ActiveBPEL, so the monitoring engine I have installed into it can read an username and run the monitoring rules associated to that username/business process pair.

According to what I've seen in the ActiveBPEL source code, HTTP basic auth should be enough for this, but AFAIK BPELUnit does not support HTTP authentication on service invocations. I think I've seen some auth on the ActiveVOSDeployer, but that's a different matter.

I think we'd only need to tweak the code that creates the HTTPClient a bit so it receives a map from (host, port, realm) triplets to (username, password) pairs, where the realm could be optional. We could specify it inside a new element in the <setUp> blocks, such as:

<setUp>
  ...

  <credentials>

    <credential host="..." port="..." [realm="..."] username="..." password="..."/>

  </credential>

</setUp>

What do you think?

Best regards,
Antonio

[Daniel Lübke]

Hi Antonio,

BPELUnit has the ability to send arbitrary HTTP headers (in every send). It's not really comfortable but you can use this to authenticate: http://en.wikipedia.org/wiki/Basic_access_authentication without the need to implement anything.

When we want to better support authentication, I'd add this to the partner. Every partner would need to be able to authenticate differently against a service - even if it has the same endpoint - when testing different roles.

Regards,
Daniel

[Antonio García Domínguez]

Hi Daniel,

Thanks! I'll look into this and see if it works for me :-). I'd like to set up these extra headers from my Java program, so I can use my previous .bpts unchanged.

Best regards,
Antonio

--
Sie haben diese Nachricht erhalten, weil Sie der Google Groups-Gruppe BPELUnit beigetreten sind.
Um Ihr Abonnement für diese Gruppe zu beenden und keine E-Mails mehr von dieser Gruppe zu erhalten, senden Sie eine Email an bpelunit+u...@googlegroups.com.
Weitere Optionen: https://groups.google.com/groups/opt_out