| Matt Milner 2005-03-03, 8:46 pm |
| The credentials stored in the SSO database do not have to be just a
password, so you can put in some other credentials as well (like a
certificate for example).
The adapter can be configured to use the affiliate application to lookup
credentials. It will do so based on the windows user that was authenticated
to the web service.
Matt
"Rania" <rania-boutros@hotmail.com> wrote in message
news:264501c51fd6$42df4cc0$a501280a@phx.gbl...
> The case is:
>
> A request would have the following steps:
>
> Portal system sends request to BizTalk through the web
> service generated by the orchestration.
> The user has been authenticated using Integrated Security
> BizTalk runs an orchestration using the input information.
> BizTalk needs to send a message out through a third-party
> adapter (affiliate application) which requires different
> credentials (and some other data dependence on the user
> using the adaptor) from the Windows account which was used
> with the Portal front-end.
>
>
> The problems are:
>
> How Does the SSO enables mapping additional parameters
> that do not exist in Windows Active directory (not only
> userid and password)
> can the send adaptor be configured as the affiliate
> application
> Are there any clear steps I can follow to accomplish that
>
>
|