Use the following as your checklist for testing this use case:
Conduct the four tests using the same browser window instance. The tests must be conducted in consecutive order to satisfy Use Case 1A.
Access the Federation Manager server using one of the following alternatives:
Go to the index.jsp URL:
https://LoadBalancer-9-siroe.com:3443/federation/saml2/jsp/index.jsp |
On the SAML2 Use Cases page, in the SP Initiated Profiles section, click the following link:
Persistent Federation (Browser Artifact) |
Go to the following URL:
https://loadbalancer-9.siroe.com:3443/federation/saml2/jsp/ spSSOInit.jsp?metaAlias=/sp&idpEntityID= loadbalancer-3.example.com |
The login request is redirected to Access Manager.
Log in to the Access Manager console using the following information:
idp
idp
The login request is redirected to Federation Manager.
Log in to the Federation Manager console using the following information:
spuser
spuser
The message “Single Sign-On succeeded” is displayed. You can view the debug file to see the actual assertion that was sent over the wire.
# vi /var/opt/SUNWam/fm/federation/debug/fmSAML2 |
Access the Federation Manager server using one of the following alternatives:
Go to the index.jsp URL:
https://LoadBalancer-9-siroe.com:3443/federation/saml2/jsp/index.jsp |
On the SAML2 Use Cases page, in the SP Initiated Profiles section, click the following link:
Logout (SOAP) |
Go to the following URL:
https://loadbalancer-9.siroe.com:3443/federation/saml2/jsp/ spSingleLogoutInit.jsp?metaAlias=/sp&binding= urn:oasis:names:tc:SAML:2.0:bindings: SOAP&idpEntityID=loadbalancer-3.example.com |
The message “SP initiated single logout succeeded” is displayed. You can view the debug file to see the actual assertion that was sent over the wire.
# vi /var/opt/SUNWam/fm/federation/debug/fmSAML2 |
Access the Federation Manager server using one of the following options:
Go to the index.jsp URL:
https://LoadBalancer-9-siroe.com:3443/federation/saml2/jsp/index.jsp |
On the SAML2 Use Cases page, in the SP Initiated Profiles section, click the following link:
Single Sign-On (Browser Artifact) |
Go to the following URL:
https://loadbalancer-9.siroe.com:3443/federation/saml2/jsp/ spSSOInit.jsp?metaAlias=/sp&idpEntityID= loadbalancer-3.example.com |
The login request is redirected to Access Manager.
Log in to the Access Manager console using the following information:
idp
idp
The message “Single Sign-On succeeded” is displayed. You can view the debug file to see the actual assertion that was sent over the wire.
# vi /var/opt/SUNWam/fm/federation/debug/fmSAML2 |
Access the Federation Manager server using one of the following alternatives:
Go to the index.jsp URL:
https://LoadBalancer-9-siroe.com:3443/federation/saml2/jsp/index.jsp |
On the SAML2 Use Cases page, in the SP Initiated Profiles section, click the following link:
Federation Termination (SOAP) |
Go to the following URL:
https://loadbalancer-9.siroe.com:3443/federation/saml2/jsp/ spMNIRequestInit.jsp?metaAlias=/sp&idpEntityID= loadbalancer-3.example.com&requestType= Terminate&binding=urn:oasis:names:tc:SAML:2.0:bindings:SOAP |
The message “ManageNameID Request succeeded” is displayed. You can view the debug file to see the actual assertion that was sent over the wire.
# vi /var/opt/SUNWam/fm/federation/debug/fmSAML2 |