Re: Liberty Browser Post Profile

Hi Shawn,

In the ID-FF protocol, the SP decides whether to use the POST or the
Artifact profile, based upon the advertised capabilities of the IDP it
is connecting to. If only one profile is advertised, then the SP must
use that profile. Otherwise, the SP can choose based upon its
convenience.

In SourceID ID-FF 1.1, if the IDP advertises support for both profiles,
then the SP will just choose the first one appearing in the list of
profiles in the metadata file (sourceid-sso-providers.xml). 

So, on the SP side, look inside sourceid-sso-providers.xml and find the
entry for the IDP. It probably contains these two lines:

<lib:SingleSignOnProtocolProfile>http://projectliberty.org/profiles/brws-art</lib:SingleSignOnProtocolProfile>
<lib:SingleSignOnProtocolProfile>http://projectliberty.org/profiles/brws-post</lib:SingleSignOnProtocolProfile>

Swap the order of these two lines as follows:

<lib:SingleSignOnProtocolProfile>http://projectliberty.org/profiles/brws-post</lib:SingleSignOnProtocolProfile>
<lib:SingleSignOnProtocolProfile>http://projectliberty.org/profiles/brws-art</lib:SingleSignOnProtocolProfile>

and then, the SP will start to use the POST profile with that IDP.

Regards,

Bryan Field-Elliot
Ping Identity Corporation


On Fri, 2005-01-21 at 07:02 -0800, Shawn McKinney wrote:

> Greetings - 
> 
> Does anyone know how to enable the demo application that is bundled
> with SourceID ID-FF 1.1 toolkit to sign-on using browser post profile?
> Our aim is to demonstrate browser post inside a website enabled
> for service provider role.
> 
> Thanks
> 
>  
> 
>  
> 
> 
> _______________________________________________
> sso-users mailing list
> [email protected]
> http://lists.sourceid.org/mailman/listinfo/sso-users

_______________________________________________
sso-users mailing list
[email protected]
http://lists.sourceid.org/mailman/listinfo/sso-users