|
Home > Archive > BizTalk Server General > May 2004 > BizTalk Deployment Wizard and HTTP ports
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
BizTalk Deployment Wizard and HTTP ports
|
|
| Brennan O'Reilly 2004-05-30, 10:46 am |
| Hello All,
I've developed a solution that makes use of an HTTP send port and is configured to communicate to the http site via an internal proxy server. The account that is entered for the internal proxy server settings is a windows domain account. I'd like to exp
ort the bindings and import the bindings in a different environment. I've sucessfully exported the bindings, however when I try to import the bindings in a different environment, It fails and I receive the following error:
Failed updating binding information. BindingException: Could not store transport type data for Primary Transport of Send Port 'MyriadRsRq' to config store. Primary SSO Server 'DEMOAPPSERVER' failed. The property bag contained a VT_NULL value to indicate t
hat the existing property value should be retained, but there is no existing value.
I've looked through the exported bindings.xml file and notice that the account name I use for the proxy server is exported however there is no password exported. I'm assuming this is by design. I'm also thinking that the error message I received is beca
use the deployment wizard is assuming I'm using an sso account that is mapped to a windows account? I'm not using SSO and haven't even looked at what that would take. Am I on the right track? I appreciate any info or advice people may have. Thanks.
-Brennan
| |
| Christof 2004-05-30, 10:46 am |
| See inline please.
Kind regards,
Christof
"Brennan O'Reilly" <anonymous@discussions.microsoft.com> wrote in message
news:414B2E45-0568-44B6-827B-68525627A8E1@microsoft.com...
> Hello All,
>
> I've developed a solution that makes use of an HTTP send port and is
configured to communicate to the http site via an internal proxy server.
The account that is entered for the internal proxy server settings is a
windows domain account. I'd like to export the bindings and import the
bindings in a different environment. I've sucessfully exported the
bindings, however when I try to import the bindings in a different
environment, It fails and I receive the following error:
>
> Failed updating binding information. BindingException: Could not store
transport type data for Primary Transport of Send Port 'MyriadRsRq' to
config store. Primary SSO Server 'DEMOAPPSERVER' failed. The property bag
contained a VT_NULL value to indicate that the existing property value
should be retained, but there is no existing value.
>
> I've looked through the exported bindings.xml file and notice that the
account name I use for the proxy server is exported however there is no
password exported. I'm assuming this is by design.
Yes this is by design. Such sensitive data like passwords is securly stored
in the SSO engine, BizTalk does not allow you to export this kind of things.
the SSO refers to the secure storage rather then a mapping between accounts
in this case.
I'm also thinking that the error message I received is because the
deployment wizard is assuming I'm using an sso account that is mapped to a
windows account? I'm not using SSO and haven't even looked at what that
would take. Am I on the right track? I appreciate any info or advice
people may have. Thanks.
>
> -Brennan
| |
| Brennan O'Reilly 2004-05-30, 10:46 am |
| Problem content snipped
--------------------------------------------------------------------------------------
> I've looked through the exported bindings.xml file and notice that the
account name I use for the proxy server is exported however there is no
password exported. I'm assuming this is by design.
Yes this is by design. Such sensitive data like passwords is securly stored
in the SSO engine, BizTalk does not allow you to export this kind of things.
the SSO refers to the secure storage rather then a mapping between accounts
in this case.
--------------------------------------------------------------------------------------
Christof what you said makes sense. However, in looking at the settings for HTTP Transport in the Authentication Tab, it seems that SSO can be used for the Creditials for example if I was planning on authenticating to a website. If set SSO here, will i
t also be used for the Proxy settings? Ideally I'd like to use anonymous authentication and SSO for the proxy settings. Thanks again for you prompt reply.
-Brennan
| |
| Christof 2004-05-30, 10:46 am |
| Should look this up, although I guess this has nothing to do with the proxy
but rather with the credentialset when doing the actual HTTP request.
Regards,
Christof
"Brennan O'Reilly" <anonymous@discussions.microsoft.com> wrote in message
news:DB53C248-0C87-420E-9598-56339050922C@microsoft.com...
> Problem content snipped
> --------------------------------------------------------------------------
------------
the[vbcol=seagreen]
> account name I use for the proxy server is exported however there is
no
> password exported. I'm assuming this is by design.
>
> Yes this is by design. Such sensitive data like passwords is securly
stored
> in the SSO engine, BizTalk does not allow you to export this kind of
things.
> the SSO refers to the secure storage rather then a mapping between
accounts
> in this case.
> --------------------------------------------------------------------------
------------
>
> Christof what you said makes sense. However, in looking at the settings
for HTTP Transport in the Authentication Tab, it seems that SSO can be used
for the Creditials for example if I was planning on authenticating to a
website. If set SSO here, will it also be used for the Proxy settings?
Ideally I'd like to use anonymous authentication and SSO for the proxy
settings. Thanks again for you prompt reply.
>
> -Brennan
| |
| Allen Zhang 2004-05-30, 10:46 am |
| You probably have found that If you remove the empty user name and password
nodes in the xml, they will deploy correctly.
SSODB is secure, encrypted db. We use that to store all configuration
informations using SSO infrastructure. SSO itself as you see in the
property pages of HTTP send, is for single sign on integration. It is not
related to secure storage of configuration data.
Hope this helps. Thanks!
- Allen Zhang (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------[vbcol=seagreen]
proxy[vbcol=seagreen]
--------------------------------------------------------------------------[vbcol=seagreen]
that[vbcol=seagreen]
is[vbcol=seagreen]
securly[vbcol=seagreen]
of[vbcol=seagreen]
--------------------------------------------------------------------------[vbcol=seagreen]
used[vbcol=seagreen]
|
|
|
|
|