|
Home > Archive > BizTalk Server > December 2006 > SSO
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]
|
|
| soulis 2006-11-17, 1:22 am |
| If SSO is configured in a Biztalk environment is it possible for a third
server to access information from that configuration?
Samples found under Biztalk 2006, like SSOApplicationConfig, so far only
work on boxes where Biztalk is installed... locally..
If I want to use the Biztalk SSO as a central config store, for say my web
server to get some info out of it... I have NO CLUE how to get at the
information stored at the Biztalk SSO.
Using .NET Id like to simply be able to just retrieve information from an
afiliate application set up at the Biztalk related SSO.. any hints pointers
would be of great help... Biztalk 2006/SSO/.NET 2.0
Thanks in advance!!
| |
| Steve Jamieson [MSFT] 2006-11-21, 7:19 pm |
| Hi -
Yes, it is. You would need to install the SSO client bits on this 3rd
server, and "point" that machine to the SSO Server you wanted to use. You
can do that using the SSO command line tools - "ssoclient -server" - this
puts a setting into the registry (NOTE - for that particular user only,
under HKCU). You can use "ssoclient -listapps" to make sure this is
working, it should list the Affiliate Applications available for the user
(on the remote SSO Server).
Hope that helps.
Steve J.
--------------------[vbcol=seagreen]
web[vbcol=seagreen]
pointers[vbcol=seagreen]
This posting is provided "AS IS" with no warranties, and confers no rights.
EBusiness Server Team
| |
| soulis 2006-11-23, 1:15 pm |
| Hi Steve,
That has been completed, however the code sample is still unable to access
the configuration information (cause the application had been set up as a
Config Store on the 'remote' server).
There was a specific error (I believe it contained the word RPC) in the
response every time I attempted to use the SSO Sample code (.NET) to access
the information on the remote machine.
Thanks
Is there any sample code that you have used, that you know retrieves remote
server information? Im sort of backtracking right now, considering using SQL
as the config data store out of concerns that the SSO deployment may be faced
with similar issues.
"Steve Jamieson [MSFT]" wrote:
> Hi -
>
> Yes, it is. You would need to install the SSO client bits on this 3rd
> server, and "point" that machine to the SSO Server you wanted to use. You
> can do that using the SSO command line tools - "ssoclient -server" - this
> puts a setting into the registry (NOTE - for that particular user only,
> under HKCU). You can use "ssoclient -listapps" to make sure this is
> working, it should list the Affiliate Applications available for the user
> (on the remote SSO Server).
>
> Hope that helps.
>
> Steve J.
>
> --------------------
> web
> pointers
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> EBusiness Server Team
>
>
| |
| Steve Jamieson [MSFT] 2006-12-11, 7:19 pm |
| Hi -
If you want to retrieve the SSO config store information remotely you
should try the following -
1. Point your client computer to the remote SSO server you want to use,
using "ssoclient -server"
2. Check that this works using "ssoclient -listapps". If that works then
your client computer is correctly communicating with the remote SSO server.
If it does not work (you get some kind of RPC error) then we need to fix
something. Possible problems - the SSO server is not running on the remote
machine - or - especially on XP SP2 or W2K3 - you may be hitting a firewall
problem or perhaps the problem indicated in KB 841893 (which prevents SSO
on XP SP2 from receiving remote calls). Configure your firewall to allow
the ENTSSO.exe service to receive calls from remote clients.
3. If this works then you should now be able to use the
ISSOConfigStore.GetConfigInfo function to read config info from your remote
SSO server. Note that this will never be able to read masked properties
remotely, they are only available locally.
Hope that helps.
--------------------[vbcol=seagreen]
<lh#w5hbDHHA.1976@TK2MSFTNGXA01.phx.gbl>[vbcol=seagreen]
access[vbcol=seagreen]
access[vbcol=seagreen]
remote[vbcol=seagreen]
SQL[vbcol=seagreen]
faced[vbcol=seagreen]
You[vbcol=seagreen]
this[vbcol=seagreen]
user[vbcol=seagreen]
third[vbcol=seagreen]
only[vbcol=seagreen]
my[vbcol=seagreen]
from an[vbcol=seagreen]
rights.[vbcol=seagreen]
This posting is provided "AS IS" with no warranties, and confers no rights.
EBusiness Server Team
|
|
|
|
|