Application Name | McGraw-Hill SAML Integration |
Publisher | McGraw-Hill |
Date Entered | 09/14/2015 |
Date Modified | 09/14/2015 |
webNetwork Version | 6.3.0.152 |
Delivery Method | SAML |
Configuration | APPLICATION
Properties Tab: Application Type : Public Context Path (Alias) : /McGrawHill Startup URL : /swPublicSSO/SAML/McGrawHill Authentication Tab: Authentication Type : SAML Identity : IDENTITYVARIABLE SAML Initiation : Identity Provider Assertion Consumer : https://aairs.tegrity.com/Service/samltest.aspx Target Resource : https://aairs.tegrity.com/Service/samltest.aspx PFX Certificate : Run through PFX Certificate Wizard TYPE - RSA 2048 Private Key : Created with PFX Certificate Wizard - export Public key Certificate : Create SHA-256 Certificate using Wizard - Save Certificate as .cer SAML Signature Location : Response SAML Logout Behavior : Full Logout Provisioning Tab: Provisioning : Enabled Provisioning Type : SAML Provisioning Parameters: email=EMAILVARIABLE familyName=SURNAMEVARIABLE givenName=GIVENNAMEVARIABLE id=IDENTITYVARIABLE role=ROLEVARIABLE |
Notes |
- Send the Public Key, and Certificate file to McGraw-Hill along with the application url of:
https://cloud.example-cloud.com/swPublicSSO/SAML/McGrawHill (replace cloud.example-cloud.com with your cloud url) - This is the setup for McGraw-Hill's test page, McGraw-Hill prefers this to first be set to the test page to hammer out details, then once things are setup the Assertion Consumer and Target Resource will change to: https://aairs.tegrity.com/Service/saml.aspx - IDENTITYVARIABLE should be something that does not change like a workforceID, employeeID, or studentID. If you use a variable that can change, then when that change takes place a new user is created on the backend and it takes a while to port over users content once McGraw-Hill is contacted. |