To clarify...
You say you are exposing services from IIB.
You say input request to these must carry a id and password.
What you don't say is how you are validating the input requests?
A typical approach would be to configure input node with security profile specifying LDAP authentication. In this way the need to authenticate is completely decoupled from the business logic of the flow. You can adapt to changes in authentication service and token types independently from the flows implementation.
However you appear to be wanting to implement your own authentication mechanism?
If you are really are, I would recommend that you do so in a way that still exploits IIB security manager and allows the validation to be configured on flows through administrative configuration of the security profile.
In addition to LDAP, IIB also supports the WS-Trust protocols to communicate with a security provider. You could exploit this standard interface to plug in your own security provider that implements the secure password store and token validation.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum