After the partnership is configured, test single sign-on between the two partners.
Testing involves:
After you test the basic partnership, you can make more changes to the sample configuration.
For testing purposes, create your own html page with a link that initiates single sign-on. You can initiate single sign-on from the IdP or SP. This example illustrates SP-initiated single sign-on.
Follow these steps:
<a href="http://sp1.demo.com:9091/affwebservices/public/
saml2authnrequest?ProviderID=idp1.example.com>
Link to Test POST Single Sign-on</a>
This link instructs the AuthnRequest Service to redirect the user to the specified Identity Provider to retrieve the authentication context.
For this sample network, the target web server is http://spapp.demo:80.
The last step that is required to test single sign-on is to create a target resource.
Follow these steps:
<p>Welcome to SP1</p>
<p>Single Sign-on is successful</p>
For this sample network, the target web server is http://spapp.demo.com:80.
After you have set up the sample web pages, test single sign-on and verify that that partnership configuration is successful.
Follow these steps:
http://spapp.demo.com:80/spsample/testsso.html
Note: In this sample network, CA SiteMinder® Federation Standalone is deployed in standalone mode, therefore, the target web server is a different server than the one where CA SiteMinder® Federation Standalone resides.
Upon entering the URL, a page appears with a link that reads Link to Test POST Single Sign-on.
Single sign-on is initiated. The user is redirected from the AuthnRequest Service at the SP to the Single Sign-on Service at the Identity Provider.
After the Identity Provider authenticates the user and establishes a session, it directs the user back to the target resource at the Service Provider, which is welcome.html. The sample welcome page that you created at the SP, lets you know the single sign-on was successful.
|
Copyright © 2014 CA.
All rights reserved.
|
|