| This webapplication will be made up of a webapplication link and a public webapplication object. It will not have a host object like many other webapps. In this example we will use the following settings: Application type : public Context path (alias) : /mysamlapp Assigned Relays : <appropriate relays to run this application> Startup url : /swPublicSSO/SAML/mysamlapp Then on the Authentication Tab for the webapplication object we have: Type : SAML Identity : Identity Provider Assertion Consumer (This is provided by your vendor) : https://url-from.3rdpartyexample-cloud.com/login.saml Target Resource (This is provided by your vendor) : https://somename.3rdpartyexample-cloud.com/sso.do Issuer (Vendor may tell you to put a specific string here) : somename Audience ( Vendor will provide this url) : https://url-from.3rdpartyexample-cloud.com/ PFX Certificate : Use the wizard to generate the certificate Private Key : Filled in when you do the wizard for the PFX Certificate Certificate : Click the wizard and fill in the information to generate the certificate. Then on the Attributes Tab. This is for sending data to the 3rd party server to provision users. Provision : Enabled Provision Type : SAML Provisioning Parameters (these would be what the 3rd party service requires): • email = @@attr:mail@@ • externalID=@@lower(typelessuserid)@@ • firstName=@@usergivenname@@ • lastName=@@usersurname@@ When the user clicks on the link for this webapplication, webNetwork would contact the service using the urls provided in the webapplication and would send the data on the provisioning tab and the vendor would exchange some certificate information and would authorize the webNetwork user to talk to the hosted service. As of 6.5, the options from the Authentication Tab and Attributes Tab now reside in a new SAML configuration editor. See the LUW 6.5 SAML Guide for more information. |