Table of Contents:
To setup SAML-based single sign-on within Azure AD, please follow the below steps:
- Step 1. Access your SAML settings in CanIPhish
- Step 2. Create an Enterprise Application in Azure AD
- Step 3. Configure SSO in CanIPhish
- Step 4. Assign the CanIPhish Application to users or groups in Azure AD
Step 1. Access your SAML settings in CanIPhish
1.1. Login to your CanIPhish Cloud Platform account and traverse to the Platform Management page.
1.2. Click on Authentication Settings > Learner Single Sign-On to show your SSO configuration.
1.3. Make a note of both the Single Sign-On URL and Audience URI values (we'll need these in the following step).
Step 2. Create an Enterprise Application in Azure AD
2.1. Login to Microsoft Azure with an admin account and visit the administrator dashboard (i.e. https://portal.azure.com/).
2.2. In the Azure dashboard click on the search bar (up the top) and run a search for "Enterprise applications", clicking on the "Enterprise applications" service that is returned.
2.3. Click the "New application" button.
2.4. Click the "Create your own application" button.
2.5. Give the app a display name of your choosing (e.g. CanIPhish Learner Dashboard), ensure the option "Integrate any other application you don't find in the gallery (Non-gallery)" is selected and click Create.
2.6. Click on the "Single sign-on" menu item on the left side of the page.
2.7. Select SAML as the single sign-on method.
2.8. Click Edit on the "Basic SAML Configuration" tile.
2.9. Enter the following information into the respective fields, leave all other fields blank, and then click Save:
Identifier (Entity ID): Audience URI (SP Entity ID) copied from CanIPhish earlier
Reply URL (Assertion Consumer Service URL): Single Sign-On URL copied from CanIPhish earlier
Sign on URL: Single Sign-On URL copied from CanIPhish earlier
2.10. Click Edit on the "Attributes & Claims" tile.
2.11. Remove the "Additional claims" for all but the top claim which is for email addresses. This can be done by clicking the "..." and then clicking Delete. The below screenshot depicts the only claim that should remain.
When viewing the claim in the claim editor, it should look as follows:
- Name: emailaddress
- Namespace: http://schemas.xmlsoap.org/ws/2005/05/identity/claims
- Source: Attribute
- Source attribute: user.mail
IMPORTANT NOTE: Please make a note of the claim name and namespace. This claim is used later to map your email address from Azure AD into CanIPhish (i.e. http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress).
2.12. Click the "SAML-based Sign-on" breadcrumb menu-item to get back to the SAML configuration page.
2.13. Within the "SAML Certificates" tile, click the Download button next to the "Federation Metadata XML" field. Make a note of the downloaded file, as we'll need it in the next step.
2.14. Click on the Properties menu item on the left side of the page. Once loaded, click "No" on the "Visible to users?" field and then click Save.
Note: Because CanIPhish only supports SP-initiated SSO, we recommend turning off "Visible to users?". This means users will need to traverse to the CanIPhish login back to then be redirected to Azure AD for authentication.
Optional: If you want to upload an App logo. A CanIPhish Logo can be downloaded here.
Step 3. Configure SSO in CanIPhish
3.1. Jump back into the CanIPhish Cloud Platform and traverse to the Platform Single Sign-On section.
3.2. Under the "Configuration For CanIPhish" section, upload the Metadata Document downloaded earlier from Azure AD. When the file is specified, click the Upload Document button.
3.4. Once successfully uploaded, you can view the document by clicking the metadata.xml text that appears.
3.5. In the "SAML Attribute Mapping (Email)" field, paste the Attribute field name we configured earlier in Azure AD (Step 2.11).
This should be: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress
3.6. By default, CanIPhish will send users an access token to log in to their learner dashboard. If SSO is configured, you could choose to Allow or Prohibit this method of access. We recommend providing users with the option to use their preferred access method and leave this as Allowed.
3.7. Click Activate SSO!
3.8. Confirm that "SSO Status" field has changed from Inactive to Active. If there are any issues, a small popup should appear notifying you of the issue.
Step 4. Assign the CanIPhish Application to users or groups in Azure AD
4.1. Jump back into the newly created "CanIPhish Cloud Platform" Azure AD Enterprise Application and then click on the "Users and groups" menu item on the left side of the page.
4.2. Click on the "Add user/group" menu button towards the top of the page.
4.3. Under the "Users and groups" menu item, click the "None Selected" hyperlink.
4.4. Depending on whether you want to assign specific Groups or Users the application, click on the respective sub-heading, select the relevant users/groups, and then click the Select button.
4.5. Click on the Assign button on the bottom left side of the page.
You're all set! Try logging in now using SSO.
Experiencing issues? Please confirm that under step 2.11 the additional claim name exactly matches the SAML Attribute Mapping listed in CanIPhish. If there is a mismatch or this additional claim doesn't exist, email addresses won't flow through correctly. Once this is correct, please Deactivate the SSO configuration and then Reactivate the SSO configuration. This resets SSO accounts on our end and will allow you to login.
Getting single sign-on setup can be complex. If you run into any issues, please don't hesitate to contact the team at CanIPhish for assistance.
Comments
0 comments
Please sign in to leave a comment.